Transmission information for a configured periodic grant of a wireless device

ABSTRACT

A wireless device receives, from a base station, at least one first message comprising a first periodicity of resources of a configured periodic grant of a first type. A request for transmission information associated with the configured periodic grant is received. A response is transmitted. The response comprises: a first value based on a number of transmissions via the resources the configured periodic grant; and a second value based on a number of times that the wireless device received no corresponding acknowledgement from the base station in response to the transmissions.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a continuation application of prior application Ser.No. 16/933,119, filed on Jul. 20, 2020, which is a continuation of priorapplication Ser. No. 16/010,218, filed Jun. 15, 2018, which has issuedas U.S. Pat. No. 10,721,025, on Jul. 21, 2020, which claims the benefitof U.S. Provisional Application No. 62/520,438, filed on Jun. 15, 2017,in the U.S. Patent and Trademark Office, which is incorporated byreference herein in its entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present inventionare described herein with reference to the drawings.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present disclosure.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers in a carrier group as per an aspect of anembodiment of the present disclosure.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present disclosure.

FIG. 4 is a block diagram of a base station and a wireless device as peran aspect of an embodiment of the present disclosure.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure.

FIG. 6 is an example diagram for a protocol structure withmulti-connectivity as per an aspect of an embodiment of the presentdisclosure.

FIG. 7 is an example diagram for a protocol structure with CA and DC asper an aspect of an embodiment of the present disclosure.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present disclosure.

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentdisclosure.

FIG. 10A and FIG. 10B are example diagrams for interfaces between a 5Gcore network (e.g. NGC) and base stations (e.g. gNB and eLTE eNB) as peran aspect of an embodiment of the present disclosure.

FIG. 11A, FIG. 11B, FIG. 11C, FIG. 11D, FIG. 11E, and FIG. 11F areexample diagrams for architectures of tight interworking between 5G RAN(e.g. gNB) and LTE RAN (e.g. (e) LTE eNB) as per an aspect of anembodiment of the present disclosure.

FIG. 12A, FIG. 12B, and FIG. 12C are example diagrams for radio protocolstructures of tight interworking bearers as per an aspect of anembodiment of the present disclosure.

FIG. 13A and FIG. 13B are example diagrams for gNB deployment scenariosas per an aspect of an embodiment of the present disclosure.

FIG. 14 is an example diagram for functional split option examples ofthe centralized gNB deployment scenario as per an aspect of anembodiment of the present disclosure.

FIG. 15A and FIG. 15B are examples of DMRS design as per an aspect of anembodiment of the present disclosure.

FIG. 16 is an example of the basic procedure of GF UL transmission witha preamble as per an aspect of an embodiment of the present disclosure.

FIG. 17A and FIG. 17B are example diagrams of preamble allocations asper an aspect of an embodiment of the present disclosure.

FIG. 18 is an example of a UE-specific hopping pattern as per an aspectof an embodiment of the present disclosure.

FIG. 19 is an example of pre-defined GF configurations comprising systemframe number and subframe number as per an aspect of an embodiment ofthe present disclosure.

FIG. 20 is an example diagram as per an aspect of an embodiment of thepresent disclosure.

FIG. 21 is an example diagram as per an aspect of an embodiment of thepresent disclosure.

FIG. 22 is an example of a decision mechanism of UL transmission via aGF radio resource that depends on a pack size as per an aspect of anembodiment of the present disclosure.

FIG. 23 is an example diagram as per an aspect of an embodiment of thepresent disclosure.

FIG. 24 is an example of GF failure report procedure as per an aspect ofan embodiment of the present disclosure.

FIG. 25 is an example diagram as per an aspect of an embodiment of thepresent disclosure.

FIG. 26 is an example diagram of a first timer and a second timer as peran aspect of an embodiment of the present disclosure.

FIG. 27 is an example of uplink power control for a GF (e.g., configuredperiodic grant of a first type) transmission as per an aspect of anembodiment of the present disclosure.

FIG. 28A, FIG. 28B, and FIG. 28C are examples of K_(PUSCH) values forTDD configuration 0-6, mapping of TPC Command Field in DCI format0/0A/0B/3/4/4A/4B/6-0A/3B to absolute and accumulated δ_(PUSCH,c)values, and mapping of TPC Command Field in DCI format 3A/3B toaccumulated δ_(PUSCH,c) values as per an aspect of an embodiment of thepresent disclosure.

FIG. 29 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 30 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 31 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 32 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 33 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 34 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 35 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 36 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 37 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 38 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present invention enable operation of carrieraggregation. Embodiments of the technology disclosed herein may beemployed in the technical field of multicarrier communication systems.More particularly, the embodiments of the technology disclosed hereinmay relate to signal timing in a multicarrier communication systems.

The following Acronyms are used throughout the present disclosure:

ASIC application-specific integrated circuit

BPSK binary phase shift keying

CA carrier aggregation

CSI channel state information

CDMA code division multiple access

CSS common search space

CPLD complex programmable logic devices

CC component carrier

CP cyclic prefix

DL downlink

DCI downlink control information

DC dual connectivity

eMBB enhanced mobile broadband

EPC evolved packet core

E-UTRAN evolved-universal terrestrial radio access network

FPGA field programmable gate arrays

FDD frequency division multiplexing

HDL hardware description languages

HARQ hybrid automatic repeat request

IE information element

LTE long term evolution

MCG master cell group

MeNB master evolved node B

MIB master information block

MAC media access control

MAC media access control

MME mobility management entity

mMTC massive machine type communications

NAS non-access stratum

NR new radio

OFDM orthogonal frequency division multiplexing

PDCP packet data convergence protocol

PDU packet data unit

PHY physical

PDCCH physical downlink control channel

PHICH physical HARQ indicator channel

PUCCH physical uplink control channel

PUSCH physical uplink shared channel

PCell primary cell

PCell primary cell

PCC primary component carrier

PSCell primary secondary cell

pTAG primary timing advance group

QAM quadrature amplitude modulation

QPSK quadrature phase shift keying

RBG resource block groups

RLC radio link control

RRC radio resource control

RA random access

RB resource blocks

SCC secondary component carrier

SCell secondary cell

Scell secondary cells

SCG secondary cell group

SeNB secondary evolved node B

sTAGs secondary timing advance group

SDU service data unit

S-GW serving gateway

SRB signaling radio bearer

SC-OFDM single carrier-OFDM

SFN system frame number

SIB system information block

TAI tracking area identifier

TAT time alignment timer

TDD time division duplexing

TDMA time division multiple access

TA timing advance

TAG timing advance group

TTI transmission time interval

TB transport block

UL uplink

UE user equipment

URLLC ultra-reliable low-latency communications

VHDL VHSIC hardware description language

CU central unit

DU distributed unit

Fs-C Fs-control plane

Fs-U Fs-user plane

gNB next generation node B

NGC next generation core

NG CP next generation control plane core

NG-C NG-control plane

NG-U NG-user plane

NR new radio

NR MAC new radio MAC

NR PHY new radio physical

NR PDCP new radio PDCP

NR RLC new radio RLC

NR RRC new radio RRC

NSSAI network slice selection assistance information

PLMN public land mobile network

UPGW user plane gateway

Xn-C Xn-control plane

Xn-U Xn-user plane

Xx-C Xx-control plane

Xx-U Xx-user plane

Example embodiments of the invention may be implemented using variousphysical layer modulation and transmission mechanisms. Exampletransmission mechanisms may include, but are not limited to: CDMA, OFDM,TDMA, Wavelet technologies, and/or the like. Hybrid transmissionmechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed.Various modulation schemes may be applied for signal transmission in thephysical layer. Examples of modulation schemes include, but are notlimited to: phase, amplitude, code, a combination of these, and/or thelike. An example radio transmission method may implement QAM using BPSK,QPSK, 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radiotransmission may be enhanced by dynamically or semi-dynamically changingthe modulation and coding scheme depending on transmission requirementsand radio conditions.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present disclosure. As illustrated inthis example, arrow(s) in the diagram may depict a subcarrier in amulticarrier OFDM system. The OFDM system may use technology such asOFDM technology, DFTS-OFDM, SC-OFDM technology, or the like. Forexample, arrow 101 shows a subcarrier transmitting information symbols.FIG. 1 is for illustration purposes, and a typical multicarrier OFDMsystem may include more subcarriers in a carrier. For example, thenumber of subcarriers in a carrier may be in the range of 10 to 10,000subcarriers. FIG. 1 shows two guard bands 106 and 107 in a transmissionband. As illustrated in FIG. 1 , guard band 106 is between subcarriers103 and subcarriers 104. The example set of subcarriers A 102 includessubcarriers 103 and subcarriers 104. FIG. 1 also illustrates an exampleset of subcarriers B 105. As illustrated, there is no guard band betweenany two subcarriers in the example set of subcarriers B 105. Carriers ina multicarrier OFDM communication system may be contiguous carriers,non-contiguous carriers, or a combination of both contiguous andnon-contiguous carriers.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers as per an aspect of an embodiment of the presentdisclosure. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 10 carriers. Carrier A 204and carrier B 205 may have the same or different timing structures.Although FIG. 2 shows two synchronized carriers, carrier A 204 andcarrier B 205 may or may not be synchronized with each other. Differentradio frame structures may be supported for FDD and TDD duplexmechanisms. FIG. 2 shows an example FDD frame timing. Downlink anduplink transmissions may be organized into radio frames 201. In thisexample, radio frame duration is 10 msec. Other frame durations, forexample, in the range of 1 to 100 msec may also be supported. In thisexample, each 10 ms radio frame 201 may be divided into ten equallysized subframes 202. Other subframe durations such as including 0.5msec, 1 msec, 2 msec, and 5 msec may also be supported. Subframe(s) maycomprise of two or more slots (e.g. slots 206 and 207). For the exampleof FDD, 10 subframes may be available for downlink transmission and 10subframes may be available for uplink transmissions in each 10 msinterval. Uplink and downlink transmissions may be separated in thefrequency domain. A slot may be 7 or 14 OFDM symbols for the samesubcarrier spacing of up to 60 kHz with normal CP. A slot may be 14 OFDMsymbols for the same subcarrier spacing higher than 60 kHz with normalCP. A slot may contain all downlink, all uplink, or a downlink part andan uplink part and/or alike. Slot aggregation may be supported, e.g.,data transmission may be scheduled to span one or multiple slots. In anexample, a mini-slot may start at an OFDM symbol in a subframe. Amini-slot may have a duration of one or more OFDM symbols. Slot(s) mayinclude a plurality of OFDM symbols 203. The number of OFDM symbols 203in a slot 206 may depend on the cyclic prefix length and subcarrierspacing.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present disclosure. The resource grid structure intime 304 and frequency 305 is illustrated in FIG. 3 . The quantity ofdownlink subcarriers or RBs may depend, at least in part, on thedownlink transmission bandwidth 306 configured in the cell. The smallestradio resource unit may be called a resource element (e.g. 301).Resource elements may be grouped into resource blocks (e.g. 302).Resource blocks may be grouped into larger radio resources calledResource Block Groups (RBG) (e.g. 303). The transmitted signal in slot206 may be described by one or several resource grids of a plurality ofsubcarriers and a plurality of OFDM symbols. Resource blocks may be usedto describe the mapping of certain physical channels to resourceelements. Other pre-defined groupings of physical resource elements maybe implemented in the system depending on the radio technology. Forexample, 24 subcarriers may be grouped as a radio block for a durationof 5 msec. In an illustrative example, a resource block may correspondto one slot in the time domain and 180 kHz in the frequency domain (for15 KHz subcarrier bandwidth and 12 subcarriers).

In an example embodiment, multiple numerologies may be supported. In anexample, a numerology may be derived by scaling a basic subcarrierspacing by an integer N. In an example, scalable numerology may allow atleast from 15 kHz to 480 kHz subcarrier spacing. The numerology with 15kHz and scaled numerology with different subcarrier spacing with thesame CP overhead may align at a symbol boundary every 1 ms in a NRcarrier.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure. FIG. 5A shows an example uplink physicalchannel. The baseband signal representing the physical uplink sharedchannel may perform the following processes. These functions areillustrated as examples and it is anticipated that other mechanisms maybe implemented in various embodiments. The functions may comprisescrambling, modulation of scrambled bits to generate complex-valuedsymbols, mapping of the complex-valued modulation symbols onto one orseveral transmission layers, transform precoding to generatecomplex-valued symbols, precoding of the complex-valued symbols, mappingof precoded complex-valued symbols to resource elements, generation ofcomplex-valued time-domain DFTS-OFDM/SC-FDMA signal for an antenna port,and/or the like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued DFTS-OFDM/SC-FDMA baseband signal for an antenna portand/or the complex-valued PRACH baseband signal is shown in FIG. 5B.Filtering may be employed prior to transmission.

An example structure for Downlink Transmissions is shown in FIG. 5C. Thebaseband signal representing a downlink physical channel may perform thefollowing processes. These functions are illustrated as examples and itis anticipated that other mechanisms may be implemented in variousembodiments. The functions include scrambling of coded bits in codewordsto be transmitted on a physical channel; modulation of scrambled bits togenerate complex-valued modulation symbols; mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers; precoding of the complex-valued modulation symbols on a layerfor transmission on the antenna ports; mapping of complex-valuedmodulation symbols for an antenna port to resource elements; generationof complex-valued time-domain OFDM signal for an antenna port, and/orthe like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued OFDM baseband signal for an antenna port is shown in FIG.5D. Filtering may be employed prior to transmission.

FIG. 4 is an example block diagram of a base station 401 and a wirelessdevice 406, as per an aspect of an embodiment of the present disclosure.A communication network 400 may include at least one base station 401and at least one wireless device 406. The base station 401 may includeat least one communication interface 402, at least one processor 403,and at least one set of program code instructions 405 stored innon-transitory memory 404 and executable by the at least one processor403. The wireless device 406 may include at least one communicationinterface 407, at least one processor 408, and at least one set ofprogram code instructions 410 stored in non-transitory memory 409 andexecutable by the at least one processor 408. Communication interface402 in base station 401 may be configured to engage in communicationwith communication interface 407 in wireless device 406 via acommunication path that includes at least one wireless link 411.Wireless link 411 may be a bi-directional link. Communication interface407 in wireless device 406 may also be configured to engage in acommunication with communication interface 402 in base station 401. Basestation 401 and wireless device 406 may be configured to send andreceive data over wireless link 411 using multiple frequency carriers.According to some of the various aspects of embodiments, transceiver(s)may be employed. A transceiver is a device that includes both atransmitter and receiver. Transceivers may be employed in devices suchas wireless devices, base stations, relay nodes, and/or the like.Example embodiments for radio technology implemented in communicationinterface 402, 407 and wireless link 411 are illustrated are FIG. 1 ,FIG. 2 , FIG. 3 , FIG. 5 , and associated text.

An interface may be a hardware interface, a firmware interface, asoftware interface, and/or a combination thereof. The hardware interfacemay include connectors, wires, electronic devices such as drivers,amplifiers, and/or the like. A software interface may include codestored in a memory device to implement protocol(s), protocol layers,communication drivers, device drivers, combinations thereof, and/or thelike. A firmware interface may include a combination of embeddedhardware and code stored in and/or in communication with a memory deviceto implement connections, electronic device operations, protocol(s),protocol layers, communication drivers, device drivers, hardwareoperations, combinations thereof, and/or the like.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics inthe device, whether the device is in an operational or non-operationalstate.

According to some of the various aspects of embodiments, a 5G networkmay include a multitude of base stations, providing a user plane NRPDCP/NR RLC/NR MAC/NR PHY and control plane (NR RRC) protocolterminations towards the wireless device. The base station(s) may beinterconnected with other base station(s) (e.g. employing an Xninterface). The base stations may also be connected employing, forexample, an NG interface to an NGC. FIG. 10A and FIG. 10B are examplediagrams for interfaces between a 5G core network (e.g. NGC) and basestations (e.g. gNB and eLTE eNB) as per an aspect of an embodiment ofthe present disclosure. For example, the base stations may beinterconnected to the NGC control plane (e.g. NG CP) employing the NG-Cinterface and to the NGC user plane (e.g. UPGW) employing the NG-Uinterface. The NG interface may support a many-to-many relation between5G core networks and base stations.

A base station may include many sectors for example: 1, 2, 3, 4, or 6sectors. A base station may include many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At RRC connectionestablishment/re-establishment/handover, one serving cell may providethe NAS (non-access stratum) mobility information (e.g. TAI), and at RRCconnection re-establishment/handover, one serving cell may provide thesecurity input. This cell may be referred to as the Primary Cell(PCell). In the downlink, the carrier corresponding to the PCell may bethe Downlink Primary Component Carrier (DL PCC), while in the uplink, itmay be the Uplink Primary Component Carrier (UL PCC). Depending onwireless device capabilities, Secondary Cells (SCells) may be configuredto form together with the PCell a set of serving cells. In the downlink,the carrier corresponding to an SCell may be a Downlink SecondaryComponent Carrier (DL SCC), while in the uplink, it may be an UplinkSecondary Component Carrier (UL SCC). An SCell may or may not have anuplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to only one cell. The cell ID or Cell index mayalso identify the downlink carrier or uplink carrier of the cell(depending on the context it is used). In the specification, cell ID maybe equally referred to a carrier ID, and cell index may be referred tocarrier index. In implementation, the physical cell ID or cell index maybe assigned to a cell. A cell ID may be determined using asynchronization signal transmitted on a downlink carrier. A cell indexmay be determined using RRC messages. For example, when thespecification refers to a first physical cell ID for a first downlinkcarrier, the specification may mean the first physical cell ID is for acell comprising the first downlink carrier. The same concept may applyto, for example, carrier activation. When the specification indicatesthat a first carrier is activated, the specification may equally meanthat the cell comprising the first carrier is activated.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, traffic load, initial systemset up, packet sizes, traffic characteristics, a combination of theabove, and/or the like. When the one or more criteria are met, variousexample embodiments may be applied. Therefore, it may be possible toimplement example embodiments that selectively implement disclosedprotocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices may support multiple technologies, and/or multiple releases ofthe same technology. Wireless devices may have some specificcapability(ies) depending on its wireless device category and/orcapability(ies). A base station may comprise multiple sectors. When thisdisclosure refers to a base station communicating with a plurality ofwireless devices, this disclosure may refer to a subset of the totalwireless devices in a coverage area. This disclosure may refer to, forexample, a plurality of wireless devices of a given LTE or 5G releasewith a given capability and in a given sector of the base station. Theplurality of wireless devices in this disclosure may refer to a selectedplurality of wireless devices, and/or a subset of total wireless devicesin a coverage area which perform according to disclosed methods, and/orthe like. There may be a plurality of wireless devices in a coveragearea that may not comply with the disclosed methods, for example,because those wireless devices perform based on older releases of LTE or5G technology.

FIG. 6 and FIG. 7 are example diagrams for protocol structure with CAand multi-connectivity as per an aspect of an embodiment of the presentdisclosure. NR may support multi-connectivity operation whereby amultiple RX/TX UE in RRC_CONNECTED may be configured to utilize radioresources provided by multiple schedulers located in multiple gNBsconnected via a non-ideal or ideal backhaul over the Xn interface. gNBsinvolved in multi-connectivity for a certain UE may assume two differentroles: a gNB may either act as a master gNB or as a secondary gNB. Inmulti-connectivity, a UE may be connected to one master gNB and one ormore secondary gNBs. FIG. 7 illustrates one example structure for the UEside MAC entities when a Master Cell Group (MCG) and a Secondary CellGroup (SCG) are configured, and it may not restrict implementation.Media Broadcast Multicast Service (MBMS) reception is not shown in thisfigure for simplicity.

In multi-connectivity, the radio protocol architecture that a particularbearer uses may depend on how the bearer is setup. Three examples ofbearers, including, an MCG bearer, an SCG bearer and a split bearer asshown in FIG. 6 . NR RRC may be located in master gNB and SRBs may beconfigured as a MCG bearer type and may use the radio resources of themaster gNB. Multi-connectivity may also be described as having at leastone bearer configured to use radio resources provided by the secondarygNB. Multi-connectivity may or may not be configured/implemented inexample embodiments of the disclosure.

In the case of multi-connectivity, the UE may be configured withmultiple NR MAC entities: one NR MAC entity for master gNB, and other NRMAC entities for secondary gNBs. In multi-connectivity, the configuredset of serving cells for a UE may comprise of two subsets: the MasterCell Group (MCG) containing the serving cells of the master gNB, and theSecondary Cell Groups (SCGs) containing the serving cells of thesecondary gNBs. For a SCG, one or more of the following may be applied:at least one cell in the SCG has a configured UL CC and one of them,named PSCell (or PCell of SCG, or sometimes called PCell), is configuredwith PUCCH resources; when the SCG is configured, there may be at leastone SCG bearer or one Split bearer; upon detection of a physical layerproblem or a random access problem on a PSCell, or the maximum number ofNR RLC retransmissions has been reached associated with the SCG, or upondetection of an access problem on a PSCell during a SCG addition or aSCG change: a RRC connection re-establishment procedure may not betriggered, UL transmissions towards cells of the SCG are stopped, amaster gNB may be informed by the UE of a SCG failure type, for splitbearer, the DL data transfer over the master gNB is maintained; the NRRLC AM bearer may be configured for the split bearer; like PCell, PSCellmay not be de-activated; PSCell may be changed with a SCG change (e.g.with security key change and a RACH procedure); and/or a direct bearertype change between a Split bearer and a SCG bearer or simultaneousconfiguration of a SCG and a Split bearer may or may not supported.

With respect to the interaction between a master gNB and secondary gNBsfor multi-connectivity, one or more of the following principles may beapplied: the master gNB may maintain the RRM measurement configurationof the UE and may, (e.g, based on received measurement reports ortraffic conditions or bearer types), decide to ask a secondary gNB toprovide additional resources (serving cells) for a UE; upon receiving arequest from the master gNB, a secondary gNB may create a container thatmay result in the configuration of additional serving cells for the UE(or decide that it has no resource available to do so); for UEcapability coordination, the master gNB may provide (part of) the ASconfiguration and the UE capabilities to the secondary gNB; the mastergNB and the secondary gNB may exchange information about a UEconfiguration by employing of NR RRC containers (inter-node messages)carried in Xn messages; the secondary gNB may initiate a reconfigurationof its existing serving cells (e.g., PUCCH towards the secondary gNB);the secondary gNB may decide which cell is the PSCell within the SCG;the master gNB may or may not change the content of the NR RRCconfiguration provided by the secondary gNB; in the case of a SCGaddition and a SCG SCell addition, the master gNB may provide the latestmeasurement results for the SCG cell(s); both a master gNB and secondarygNBs may know the SFN and subframe offset of each other by OAM, (e.g.,for the purpose of DRX alignment and identification of a measurementgap). In an example, when adding a new SCG SCell, dedicated NR RRCsignaling may be used for sending required system information of thecell as for CA, except for the SFN acquired from a MIB of the PSCell ofa SCG.

In an example, serving cells may be grouped in a TA group (TAG). Servingcells in one TAG may use the same timing reference. For a given TAG,user equipment (UE) may use at least one downlink carrier as a timingreference. For a given TAG, a UE may synchronize uplink subframe andframe transmission timing of uplink carriers belonging to the same TAG.In an example, serving cells having an uplink to which the same TAapplies may correspond to serving cells hosted by the same receiver. AUE supporting multiple TAs may support two or more TA groups. One TAgroup may contain the PCell and may be called a primary TAG (pTAG). In amultiple TAG configuration, at least one TA group may not contain thePCell and may be called a secondary TAG (sTAG). In an example, carrierswithin the same TA group may use the same TA value and/or the sametiming reference. When DC is configured, cells belonging to a cell group(MCG or SCG) may be grouped into multiple TAGs including a pTAG and oneor more sTAGs.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present disclosure. In Example 1, pTAG comprisesPCell, and an sTAG comprises SCell1. In Example 2, a pTAG comprises aPCell and SCell1, and an sTAG comprises SCell2 and SCell3. In Example 3,pTAG comprises PCell and SCell1, and an sTAG1 includes SCell2 andSCell3, and sTAG2 comprises SCell4. Up to four TAGs may be supported ina cell group (MCG or SCG) and other example TAG configurations may alsobe provided. In various examples in this disclosure, example mechanismsare described for a pTAG and an sTAG. Some of the example mechanisms maybe applied to configurations with multiple sTAGs.

In an example, an eNB may initiate an RA procedure via a PDCCH order foran activated SCell. This PDCCH order may be sent on a scheduling cell ofthis SCell. When cross carrier scheduling is configured for a cell, thescheduling cell may be different than the cell that is employed forpreamble transmission, and the PDCCH order may include an SCell index.At least a non-contention based RA procedure may be supported forSCell(s) assigned to sTAG(s).

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentdisclosure. An eNB transmits an activation command 600 to activate anSCell. A preamble 602 (Msg1) may be sent by a UE in response to a PDCCHorder 601 on an SCell belonging to an sTAG. In an example embodiment,preamble transmission for SCells may be controlled by the network usingPDCCH format 1A. Msg2 message 603 (RAR: random access response) inresponse to the preamble transmission on the SCell may be addressed toRA-RNTI in a PCell common search space (CSS). Uplink packets 604 may betransmitted on the SCell in which the preamble was transmitted.

According to some of the various aspects of embodiments, initial timingalignment may be achieved through a random access procedure. This mayinvolve a UE transmitting a random access preamble and an eNB respondingwith an initial TA command NTA (amount of timing advance) within arandom access response window. The start of the random access preamblemay be aligned with the start of a corresponding uplink subframe at theUE assuming NTA=0. The eNB may estimate the uplink timing from therandom access preamble transmitted by the UE. The TA command may bederived by the eNB based on the estimation of the difference between thedesired UL timing and the actual UL timing. The UE may determine theinitial uplink transmission timing relative to the correspondingdownlink of the sTAG on which the preamble is transmitted.

The mapping of a serving cell to a TAG may be configured by a servingeNB with RRC signaling. The mechanism for TAG configuration andreconfiguration may be based on RRC signaling. According to some of thevarious aspects of embodiments, when an eNB performs an SCell additionconfiguration, the related TAG configuration may be configured for theSCell. In an example embodiment, an eNB may modify the TAG configurationof an SCell by removing (releasing) the SCell and adding (configuring) anew SCell (with the same physical cell ID and frequency) with an updatedTAG ID. The new SCell with the updated TAG ID may initially be inactivesubsequent to being assigned the updated TAG ID. The eNB may activatethe updated new SCell and start scheduling packets on the activatedSCell. In an example implementation, it may not be possible to changethe TAG associated with an SCell, but rather, the SCell may need to beremoved and a new SCell may need to be added with another TAG. Forexample, if there is a need to move an SCell from an sTAG to a pTAG, atleast one RRC message, for example, at least one RRC reconfigurationmessage, may be send to the UE to reconfigure TAG configurations byreleasing the SCell and then configuring the SCell as a part of the pTAG(when an SCell is added/configured without a TAG index, the SCell may beexplicitly assigned to the pTAG). The PCell may not change its TA groupand may be a member of the pTAG.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g. to establish, modify and/or release RBs,to perform handover, to setup, modify, and/or release measurements, toadd, modify, and/or release SCells). If the received RRC ConnectionReconfiguration message includes the sCellToReleaseList, the UE mayperform an SCell release. If the received RRC Connection Reconfigurationmessage includes the sCellToAddModList, the UE may perform SCelladditions or modification.

In LTE Release-10 and Release-11 CA, a PUCCH is only transmitted on thePCell (PSCell) to an eNB. In LTE-Release 12 and earlier, a UE maytransmit PUCCH information on one cell (PCell or PSCell) to a given eNB.

As the number of CA capable UEs and also the number of aggregatedcarriers increase, the number of PUCCHs and also the PUCCH payload sizemay increase. Accommodating the PUCCH transmissions on the PCell maylead to a high PUCCH load on the PCell. A PUCCH on an SCell may beintroduced to offload the PUCCH resource from the PCell. More than onePUCCH may be configured for example, a PUCCH on a PCell and anotherPUCCH on an SCell. In the example embodiments, one, two or more cellsmay be configured with PUCCH resources for transmitting CSI/ACK/NACK toa base station. Cells may be grouped into multiple PUCCH groups, and oneor more cell within a group may be configured with a PUCCH. In anexample configuration, one SCell may belong to one PUCCH group. SCellswith a configured PUCCH transmitted to a base station may be called aPUCCH SCell, and a cell group with a common PUCCH resource transmittedto the same base station may be called a PUCCH group.

In an example embodiment, a MAC entity may have a configurable timertimeAlignmentTimer per TAG. The timeAlignmentTimer may be used tocontrol how long the MAC entity considers the Serving Cells belonging tothe associated TAG to be uplink time aligned. The MAC entity may, when aTiming Advance Command MAC control element is received, apply the TimingAdvance Command for the indicated TAG; start or restart thetimeAlignmentTimer associated with the indicated TAG. The MAC entitymay, when a Timing Advance Command is received in a Random AccessResponse message for a serving cell belonging to a TAG and/or if theRandom Access Preamble was not selected by the MAC entity, apply theTiming Advance Command for this TAG and start or restart thetimeAlignmentTimer associated with this TAG. Otherwise, if thetimeAlignmentTimer associated with this TAG is not running, the TimingAdvance Command for this TAG may be applied and the timeAlignmentTimerassociated with this TAG started. When the contention resolution isconsidered not successful, a timeAlignmentTimer associated with this TAGmay be stopped. Otherwise, the MAC entity may ignore the received TimingAdvance Command.

In example embodiments, a timer is running once it is started, until itis stopped or until it expires; otherwise it may not be running. A timercan be started if it is not running or restarted if it is running. Forexample, a timer may be started or restarted from its initial value.

Example embodiments of the disclosure may enable operation ofmulti-carrier communications. Other example embodiments may comprise anon-transitory tangible computer readable media comprising instructionsexecutable by one or more processors to cause operation of multi-carriercommunications. Yet other example embodiments may comprise an article ofmanufacture that comprises a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g. wirelesscommunicator, UE, base station, etc.) to enable operation ofmulti-carrier communications. The device may include processors, memory,interfaces, and/or the like. Other example embodiments may comprisecommunication networks comprising devices such as base stations,wireless devices (or user equipment: UE), servers, switches, antennas,and/or the like.

FIG. 11A, FIG. 11B, FIG. 11C, FIG. 11D, FIG. 11E, and FIG. 11F areexample diagrams for architectures of tight interworking between 5G RANand LTE RAN as per an aspect of an embodiment of the present disclosure.The tight interworking may enable a multiple RX/TX UE in RRC_CONNECTEDto be configured to utilize radio resources provided by two schedulerslocated in two base stations (e.g. (e) LTE eNB and gNB) connected via anon-ideal or ideal backhaul over the Xx interface between LTE eNB andgNB or the Xn interface between eLTE eNB and gNB. Base stations involvedin tight interworking for a certain UE may assume two different roles: abase station may either act as a master base station or as a secondarybase station. In tight interworking, a UE may be connected to one masterbase station and one secondary base station. Mechanisms implemented intight interworking may be extended to cover more than two base stations.

In FIG. 11A and FIG. 11B, a master base station may be an LTE eNB, whichmay be connected to EPC nodes (e.g. to an MME via the S1-C interface andto an S-GW via the S1-U interface), and a secondary base station may bea gNB, which may be a non-standalone node having a control planeconnection via an Xx-C interface to an LTE eNB. In the tightinterworking architecture of FIG. 11A, a user plane for a gNB may beconnected to an S-GW through an LTE eNB via an Xx-U interface betweenLTE eNB and gNB and an S1-U interface between LTE eNB and S-GW. In thearchitecture of FIG. 11B, a user plane for a gNB may be connecteddirectly to an S-GW via an S1-U interface between gNB and S-GW.

In FIG. 11C and FIG. 11D, a master base station may be a gNB, which maybe connected to NGC nodes (e.g. to a control plane core node via theNG-C interface and to a user plane core node via the NG-U interface),and a secondary base station may be an eLTE eNB, which may be anon-standalone node having a control plane connection via an Xn-Cinterface to a gNB. In the tight interworking architecture of FIG. 11C,a user plane for an eLTE eNB may be connected to a user plane core nodethrough a gNB via an Xn-U interface between eLTE eNB and gNB and an NG-Uinterface between gNB and user plane core node. In the architecture ofFIG. 11D, a user plane for an eLTE eNB may be connected directly to auser plane core node via an NG-U interface between eLTE eNB and userplane core node.

In FIG. 11E and FIG. 11F, a master base station may be an eLTE eNB,which may be connected to NGC nodes (e.g. to a control plane core nodevia the NG-C interface and to a user plane core node via the NG-Uinterface), and a secondary base station may be a gNB, which may be anon-standalone node having a control plane connection via an Xn-Cinterface to an eLTE eNB. In the tight interworking architecture of FIG.11E, a user plane for a gNB may be connected to a user plane core nodethrough an eLTE eNB via an Xn-U interface between eLTE eNB and gNB andan NG-U interface between eLTE eNB and user plane core node. In thearchitecture of FIG. 11F, a user plane for a gNB may be connecteddirectly to a user plane core node via an NG-U interface between gNB anduser plane core node.

FIG. 12A, FIG. 12B, and FIG. 12C are example diagrams for radio protocolstructures of tight interworking bearers as per an aspect of anembodiment of the present disclosure. In FIG. 12A, an LTE eNB may be amaster base station, and a gNB may be a secondary base station. In FIG.12B, a gNB may be a master base station, and an eLTE eNB may be asecondary base station. In FIG. 12C, an eLTE eNB may be a master basestation, and a gNB may be a secondary base station. In 5G network, theradio protocol architecture that a particular bearer uses may depend onhow the bearer is setup. Three example bearers including an MCG bearer,an SCG bearer, and a split bearer as shown in FIG. 12A, FIG. 12B, andFIG. 12C. NR RRC may be located in master base station, and SRBs may beconfigured as an MCG bearer type and may use the radio resources of themaster base station. Tight interworking may also be described as havingat least one bearer configured to use radio resources provided by thesecondary base station. Tight interworking may or may not beconfigured/implemented in example embodiments of the disclosure.

In the case of tight interworking, the UE may be configured with two MACentities: one MAC entity for master base station, and one MAC entity forsecondary base station. In tight interworking, the configured set ofserving cells for a UE may comprise of two subsets: the Master CellGroup (MCG) containing the serving cells of the master base station, andthe Secondary Cell Group (SCG) containing the serving cells of thesecondary base station. For a SCG, one or more of the following may beapplied: at least one cell in the SCG has a configured UL CC and one ofthem, named PSCell (or PCell of SCG, or sometimes called PCell), isconfigured with PUCCH resources; when the SCG is configured, there maybe at least one SCG bearer or one split bearer; upon detection of aphysical layer problem or a random access problem on a PSCell, or themaximum number of (NR) RLC retransmissions has been reached associatedwith the SCG, or upon detection of an access problem on a PSCell duringa SCG addition or a SCG change: a RRC connection re-establishmentprocedure may not be triggered, UL transmissions towards cells of theSCG are stopped, a master base station may be informed by the UE of aSCG failure type, for split bearer, the DL data transfer over the masterbase station is maintained; the RLC AM bearer may be configured for thesplit bearer; like PCell, PSCell may not be de-activated; PSCell may bechanged with a SCG change (e.g. with security key change and a RACHprocedure); and/or neither a direct bearer type change between a Splitbearer and a SCG bearer nor simultaneous configuration of a SCG and aSplit bearer are supported.

With respect to the interaction between a master base station and asecondary base station, one or more of the following principles may beapplied: the master base station may maintain the RRM measurementconfiguration of the UE and may, (e.g, based on received measurementreports, traffic conditions, or bearer types), decide to ask a secondarybase station to provide additional resources (serving cells) for a UE;upon receiving a request from the master base station, a secondary basestation may create a container that may result in the configuration ofadditional serving cells for the UE (or decide that it has no resourceavailable to do so); for UE capability coordination, the master basestation may provide (part of) the AS configuration and the UEcapabilities to the secondary base station; the master base station andthe secondary base station may exchange information about a UEconfiguration by employing of RRC containers (inter-node messages)carried in Xn or Xx messages; the secondary base station may initiate areconfiguration of its existing serving cells (e.g., PUCCH towards thesecondary base station); the secondary base station may decide whichcell is the PSCell within the SCG; the master base station may notchange the content of the RRC configuration provided by the secondarybase station; in the case of a SCG addition and a SCG SCell addition,the master base station may provide the latest measurement results forthe SCG cell(s); both a master base station and a secondary base stationmay know the SFN and subframe offset of each other by OAM, (e.g., forthe purpose of DRX alignment and identification of a measurement gap).In an example, when adding a new SCG SCell, dedicated RRC signaling maybe used for sending required system information of the cell as for CA,except for the SFN acquired from a MIB of the PSCell of a SCG.

FIG. 13A and FIG. 13B are example diagrams for gNB deployment scenariosas per an aspect of an embodiment of the present disclosure. In thenon-centralized deployment scenario in FIG. 13A, the full protocol stack(e.g. NR RRC, NR PDCP, NR RLC, NR MAC, and NR PHY) may be supported atone node. In the centralized deployment scenario in FIG. 13B, upperlayers of gNB may be located in a Central Unit (CU), and lower layers ofgNB may be located in Distributed Units (DU). The CU-DU interface (e.g.Fs interface) connecting CU and DU may be ideal or non-ideal. Fs-C mayprovide a control plane connection over Fs interface, and Fs-U mayprovide a user plane connection over Fs interface. In the centralizeddeployment, different functional split options between CU and DUs may bepossible by locating different protocol layers (RAN functions) in CU andDU. The functional split may support flexibility to move RAN functionsbetween CU and DU depending on service requirements and/or networkenvironments. The functional split option may change during operationafter Fs interface setup procedure, or may change only in Fs setupprocedure (i.e. static during operation after Fs setup procedure).

FIG. 14 is an example diagram for different functional split optionexamples of the centralized gNB deployment scenario as per an aspect ofan embodiment of the present disclosure. In the split option example 1,an NR RRC may be in CU, and NR PDCP, NR RLC, NR MAC, NR PHY, and RF maybe in DU. In the split option example 2, an NR RRC and NR PDCP may be inCU, and NR RLC, NR MAC, NR PHY, and RF may be in DU. In the split optionexample 3, an NR RRC, NR PDCP, and partial function of NR RLC may be inCU, and the other partial function of NR RLC, NR MAC, NR PHY, and RF maybe in DU. In the split option example 4, an NR RRC, NR PDCP, and NR RLCmay be in CU, and NR MAC, NR PHY, and RF may be in DU. In the splitoption example 5, an NR RRC, NR PDCP, NR RLC, and partial function of NRMAC may be in CU, and the other partial function of NR MAC, NR PHY, andRF may be in DU. In the split option example 6, an NR RRC, NR PDCP, NRRLC, and NR MAC may be in CU, and NR PHY and RF may be in DU. In thesplit option example 7, an NR RRC, NR PDCP, NR RLC, NR MAC, and partialfunction of NR PHY may be in CU, and the other partial function of NRPHY and RF may be in DU. In the split option example 8, an NR RRC, NRPDCP, NR RLC, NR MAC, and NR PHY may be in CU, and RF may be in DU.

The functional split may be configured per CU, per DU, per UE, perbearer, per slice, or with other granularities. In per CU split, a CUmay have a fixed split, and DUs may be configured to match the splitoption of CU. In per DU split, a DU may be configured with a differentsplit, and a CU may provide different split options for different DUs.In per UE split, a gNB (CU and DU) may provide different split optionsfor different UEs. In per bearer split, different split options may beutilized for different bearer types. In per slice splice, differentsplit options may be applied for different slices.

In an example embodiment, the new radio access network (new RAN) maysupport different network slices, which may allow differentiatedtreatment customized to support different service requirements with endto end scope. The new RAN may provide a differentiated handling oftraffic for different network slices that may be pre-configured, and mayallow a single RAN node to support multiple slices. The new RAN maysupport selection of a RAN part for a given network slice, by one ormore slice ID(s) or NSSAI(s) provided by a UE or a NGC (e.g. NG CP). Theslice ID(s) or NSSAI(s) may identify one or more of pre-configurednetwork slices in a PLMN. For initial attach, a UE may provide a sliceID and/or an NSSAI, and a RAN node (e.g. gNB) may use the slice ID orthe NSSAI for routing an initial NAS signaling to an NGC control planefunction (e.g. NG CP). If a UE does not provide any slice ID or NSSAI, aRAN node may send a NAS signaling to a default NGC control planefunction. For subsequent accesses, the UE may provide a temporary ID fora slice identification, which may be assigned by the NGC control planefunction, to enable a RAN node to route the NAS message to a relevantNGC control plane function. The new RAN may support resource isolationbetween slices. The RAN resource isolation may be achieved by avoidingthat shortage of shared resources in one slice breaks a service levelagreement for another slice.

The amount of data traffic carried over cellular networks is expected toincrease for many years to come. The number of users/devices isincreasing and a user/device accesses an increasing number and varietyof services, e.g. video delivery, large files, images. This requiresprovisioning a high data rates and capacity in the network to meetcustomers' expectations. More spectrum is therefore needed for cellularoperators to meet the increasing demand. Considering user expectationsof high data rates along with seamless mobility, it is beneficial thatmore spectrum be made available for deploying macro cells as well assmall cells for cellular systems.

Striving to meet the market demands, there has been increasing interestfrom operators in deploying some complementary access utilizingunlicensed spectrum to meet the traffic growth. This is exemplified bythe large number of operator-deployed Wi-Fi networks and the 3GPPstandardization of LTE/WLAN interworking solutions. This interestindicates that unlicensed spectrum, when present, can be an effectivecomplement to licensed spectrum for cellular operators to helpaddressing the traffic explosion in some scenarios, such as hotspotareas. LAA offers an option for operators to make use of unlicensedspectrum while managing one radio network, thus offering newpossibilities for optimizing the network's efficiency.

In an example embodiment, Listen-before-talk (clear channel assessment)may be implemented for transmission in an LAA cell. In alisten-before-talk (LBT) procedure, equipment may apply a clear channelassessment (CCA) check before using the channel. For example, the CCAutilizes at least energy detection to determine the presence or absenceof other signals on a channel in order to determine if a channel isoccupied or clear, respectively. For example, European and Japaneseregulations mandate the usage of LBT in the unlicensed bands. Apart fromregulatory requirements, carrier sensing via LBT may be one way for fairsharing of the unlicensed spectrum.

In an example embodiment, discontinuous transmission on an unlicensedcarrier with limited maximum transmission duration may be enabled. Someof these functions may be supported by one or more signals to betransmitted from the beginning of a discontinuous LAA downlinktransmission. Channel reservation may be enabled by the transmission ofsignals, by an LAA node, after gaining channel access via a successfulLBT operation, so that other nodes that receive the transmitted signalwith energy above a certain threshold sense the channel to be occupied.Functions that may need to be supported by one or more signals for LAAoperation with discontinuous downlink transmission may include one ormore of the following: detection of the LAA downlink transmission(including cell identification) by UEs; time & frequency synchronizationof UEs.

In an example embodiment, DL LAA design may employ subframe boundaryalignment according to LTE-A carrier aggregation timing relationshipsacross serving cells aggregated by CA. This may not imply that the eNBtransmissions can start only at the subframe boundary. LAA may supporttransmitting PDSCH when not all OFDM symbols are available fortransmission in a subframe according to LBT. Delivery of controlinformation for the PDSCH may be supported.

LBT procedure may be employed for fair and friendly coexistence of LAAwith other operators and technologies operating in unlicensed spectrum.LBT procedures on a node attempting to transmit on a carrier inunlicensed spectrum require the node to perform a clear channelassessment to determine if the channel is free for use. An LBT proceduremay involve at least energy detection to determine if the channel isbeing used. For example, regulatory requirements in some regions, e.g.,in Europe, specify an energy detection threshold such that if a nodereceives energy greater than this threshold, the node assumes that thechannel is not free. While nodes may follow such regulatoryrequirements, a node may optionally use a lower threshold for energydetection than that specified by regulatory requirements. In an example,LAA may employ a mechanism to adaptively change the energy detectionthreshold, e.g., LAA may employ a mechanism to adaptively lower theenergy detection threshold from an upper bound. Adaptation mechanism maynot preclude static or semi-static setting of the threshold. In anexample Category 4 LBT mechanism or other type of LBT mechanisms may beimplemented.

Various example LBT mechanisms may be implemented. In an example, forsome signals, in some implementation scenarios, in some situations,and/or in some frequencies no LBT procedure may performed by thetransmitting entity. In an example, Category 2 (e.g. LBT without randomback-off) may be implemented. The duration of time that the channel issensed to be idle before the transmitting entity transmits may bedeterministic. In an example, Category 3 (e.g. LBT with random back-offwith a contention window of fixed size) may be implemented. The LBTprocedure may have the following procedure as one of its components. Thetransmitting entity may draw a random number N within a contentionwindow. The size of the contention window may be specified by theminimum and maximum value of N. The size of the contention window may befixed. The random number N may be employed in the LBT procedure todetermine the duration of time that the channel is sensed to be idlebefore the transmitting entity transmits on the channel. In an example,Category 4 (e.g. LBT with random back-off with a contention window ofvariable size) may be implemented. The transmitting entity may draw arandom number N within a contention window. The size of contentionwindow may be specified by the minimum and maximum value of N. Thetransmitting entity may vary the size of the contention window whendrawing the random number N. The random number N is used in the LBTprocedure to determine the duration of time that the channel is sensedto be idle before the transmitting entity transmits on the channel.

LAA may employ uplink LBT at the UE. The UL LBT scheme may be differentfrom the DL LBT scheme (e.g. by using different LBT mechanisms orparameters) for example, since the LAA UL is based on scheduled accesswhich affects a UE's channel contention opportunities. Otherconsiderations motivating a different UL LBT scheme include, but are notlimited to, multiplexing of multiple UEs in a single subframe.

In an example, a DL transmission burst may be a continuous transmissionfrom a DL transmitting node with no transmission immediately before orafter from the same node on the same CC. An UL transmission burst from aUE perspective may be a continuous transmission from a UE with notransmission immediately before or after from the same UE on the sameCC. In an example, UL transmission burst is defined from a UEperspective. In an example, an UL transmission burst may be defined froman eNB perspective. In an example, in case of an eNB operating DL+UL LAAover the same unlicensed carrier, DL transmission burst(s) and ULtransmission burst(s) on LAA may be scheduled in a TDM manner over thesame unlicensed carrier. For example, an instant in time may be part ofa DL transmission burst or an UL transmission burst.

In example embodiments, two types of configured grants may beimplemented in a wireless network. In a first type of configured grantone or more RRC messages transmitted by a base station may configure andactivate/initialize a grant-free uplink process. In a second type ofconfigured grant one or more RRC messages transmitted by a base stationmay configure at least one semi-persistent scheduling grant. In a secondtype of configured period grant, the base station may transmit L1/L2signaling (e.g. DCI indicating SPS activation) to activate at least oneSPS grant. These two types of uplink transmissions by a wireless deviceis performed without receiving a dynamic grant (e.g. DCI grants). In anexample, in a configured grant of the first type (also called grant-freeprocess) configured uplink radio resources may be shared by multiplewireless devices. In an example, in a configured grant of the secondtype (also called semi-persistent scheduling) configured uplink radioresources may be allocated to one wireless device. In thisspecification, the configured grant of the first type is referred to agrant free transmission, process, and/or operation. The configured grantof the second type is referred to semi-persistent scheduling.

A new radio (NR) may support uplink (UL) transmissions without a dynamicUL grant for one or more service types, e.g., ultra-reliable low latencycommunications (URLLC). A base station (e.g. a gNB) may configure thetime and frequency radio resource(s) for the GF UL transmission(configured grant of the first type). A UE configured by the gNB to usethe GF UL radio resources may transmit one or more data packets withouta dynamic UL grant, which may result in reducing the signaling overheadcomparing with a grant-based (GB) UL transmission. Such a service typethat may need strict requirements, especially in terms of latency andreliability. URLLC may be a candidate for which a UE may use the GF ULtransmission.

The GF UL transmission may support multiple user equipment (UEs)accessing the same radio resources in order to achieve lower latency andlower signaling overhead than a GB UL transmission. A GF radio resourcepool may be employed as a subset of radio resources from a common radioresource set (e.g. from uplink shared channel radio resources). Theradio resource pool may be used to allocate exclusive or partiallyoverlapped radio resources for GF UL transmissions in a cell or toorganize frequency/time reuse between different cells or parts of a cell(e.g. cell-center and cell-edge).

If a gNB configures multiple UEs with the same GF radio resource pool,there may be a collision between two or more UEs on their GF ULtransmission. The collision at the same GF radio resources may beavoidable based on UE specific demodulation reference signal (DMRS)parameters that are distinguishable at the gNB, e.g., the root index ifZadoff-Chu (ZC) sequences are adopted, cyclic shift (CS) index, TDM/FDMpattern index if any, orthogonal cover code (OCC) sequences or index.The gNB may configure the UE specific DMRS parameters along with thetime/frequency radio resources for the UE.

In an example, FIG. 15A and FIG. 15B are two examples of DMRS design.FIG. 15A is an example with 4 UEs multiplexed on at least one DMRSsymbol. The DMRS of 4 UEs are plotted with different patterns. FIG. 15Bis an example with 2 DMRS symbols out of 14 orthogonalfrequency-division multiplexing (OFDM) symbols. FIG. 15A is a combpattern used to divide resource elements (REs) in one symbol into DMRSRE groups, and a UE occupies a group of REs to transmit its DMRS.Channel estimation and related measurements is based on orthogonal DMRSof multiplexed UEs. FIG. 15B is a Zadoff-Chu (ZC) sequence withdifferent cyclic shifts used to accommodate multiple UEs' DMRSs in thesame OFDM symbol. In this way, the channel impulse response (CIR) ofmultiplexed UEs may be delayed and be separated in time domain, whichmay facilitate channel estimation and measurements. In an example, thelocation of DMRS in FIG. 15A follows legacy LTE design, which is anexample only. In an example, DMRS for URLLC may be put on the first 2OFDM symbols.

To identify a UE ID from the collision over the same GF radio resourcepool, instead of DMRS, a gNB may use a preamble sequence that may betransmitted together with the PUSCH data. The preamble may be designedto be reliable and to meet the detection requirement of a service, e.g.,URLLC. FIG. 16 is an example of a procedure of GF UL transmission with apreamble transmission. UE may start a GF UL transmission in theconfigured radio resources when there is a packet in the UE buffer, asshown in FIG. 16 . The UE may transmit a preamble together with the datablock in the first step and receive a response in the second step. Thedata may be repeated K times depending on a gNB configuration. Thepreamble may not be repeated as long as it is reliable enough. Theresponse from a gNB may be a UL grant or a dedicated ACK/NACKtransmitted in the downlink control information (DCI).

For UEs configured with a GF radio resource pool, a preamble sequencemay be uniquely allocated to a UE with the assumption that the number ofUEs sharing the same GF radio resources is smaller than the number ofavailable preamble sequences. This may be the typical case consideringthat the number of URLLC UEs in a cell may not be large. In addition,the gNB may configure different GF radio resources for different sets ofUEs such that the preamble sequences may be reused in different GF radioresources.

In an example, preamble sequences may be mutually orthogonal, e.g. thepreamble sequences may have different cyclic shifts of a ZC rootsequence. The preamble sequence transmitted with data may be employed asreference signals for demodulating the data. In an example, a number ofREs may be employed for the preamble transmission. For example, a largenumber of REs employed for the preamble transmission may improvereliability in UE ID detection. A gNB may configure a number of OFDMsymbols for preamble transmission in time domain and a bandwidth infrequency domain, depending on whether DMRS may provide reliabledetection performance. For example, two sets of UEs may share the samepreamble transmission bandwidth with different data transmissionbandwidth, e.g., the preambles of two sets of UEs are multiplexed in thesame radio resources. The REs carrying the preamble that are within thebandwidth for GF UL data transmission may be employed as referencesignals for GF data demodulation. The preambles that are transmittedoutside of GF data bandwidth may be orthogonally multiplexed with theDMRS of a GB UE. This may reduce the impact to GB UEs.

FIG. 17A and FIG. 17B illustrate an example. In FIG. 17A, one mini-slotcontains 4 OFDM symbols and gNB configures two OFDM symbols for thepreamble transmission. In FIG. 17B, 3 OFDM symbols are contained in onemini-slot, and the preamble is configured to transmit in 1 OFDM symbol,but in larger transmission bandwidth than the data transmission.

For the GF UL transmission, a gNB may support a K-repetition of the sametransport block (TB) transmission over the GF radio resource or GF radioresource pool. A wireless device may repeat the transmission of TB untilone or more conditions are met. For example, the wireless device maycontinue the repetitions upto K times for the same TB until one of thefollowing conditions is met: If an UL grant is successfully received forthe same TB, the number of repetitions for the TB reaches K, othertermination condition of repetition may apply. The number of maximumrepetitions, K, may be a configurable parameter that may be UE-specific,and/or cell-specific.

A mini-slot or a symbol may be a unit of the K-repetition. A gNB maytransmit at least one radio resource control message to configure thenumber of repetition and the radio resource. The network may assume aset of initial transmission and the repetition as one amount of thetransmission. Initial transmission and its repetition may be implementedas an extended TTI. These repetitions may not be contiguous in time. Iftransmissions are contiguous, it may allow coherent combining. Iftransmissions are not contiguous, it may allow time diversity.

For example, one or more UEs' GF UL transmissions may collide in thesame GF radio resource, e.g., when a gNB configure the one or more UEsto share the GF radio resources. A gNB may fail to detect data of theone or more UEs colliding in the same GF radio resource. The one or moreUEs may retransmit the data without dynamic UL grants via the GF radioresource. The one or more UEs may collide again during theretransmission. Hopping (e.g., over time and/or frequency domain) mayavoid the collision problem when GF radio resources are shared bymultiple UEs. Hopping may randomize the collision relationship betweenUEs within a time interval, thus avoiding persistent collision. It mayprovide a diversity gain on the frequency domain. A UE-specific hoppingpattern may be semi-statistically configured by a gNB. FIG. 18 is anexample of a UE-specific hopping pattern.

One or more factors may be considered for the hopping pattern design,for example, the number of resource units (RUs), the maximum number ofUEs sharing the same RU, the recently used RU index, the recent hoppingindex or the current slot index, the information indicating recentlyused sequence, hopping pattern or hopping rule, etc. The sequencedescribed above may be a DMRS, a spreading sequence, or a preamblesequence that may be UE-specific.

The gNB may support to switch between GF and GB UL transmissions tobalance resource utilization and delay/reliability requirements ofassociated services. The GF UL transmission may be based on asemi-static resource configuration that may reduce latency.

To support the switching between GF and GB UL transmissions, the initialtransmission on the pre-configured GF radio resources may include UEidentification (ID), for example, explicit UE ID information (e.g.C-RNTI) or implicit UE information such as a DMRS cyclic shift (assuminguse of ZC sequences) specific signature. To inform a gNB of whether theUE has remaining data to transmit, the UE may include buffer statusreporting (BSR) with the initial data transmission. If a gNBsuccessfully decodes data transmitted by a UE and determines that the UEhas remaining data to transmit (e.g. from a BSR report), the gNB mayswitch scheduling for a UE from GF to GB UL transmissions. If a gNBfails to decode data transmitted by the UE but successfully detects theUE ID from the uniquely assigned sequence (e.g., preamble and/or DMRS),the gNB may switch scheduling for UE from GF to GB UL transmissions. TheUL grant for subsequent data transmissions may be with CRC scrambled bythe UE C-RNTI (may be determined either by explicit signaling in theinitial transmission or implicitly by the DMRS cyclic shift).

One of the termination conditions for the K-repetitions may be areception of a UL grant which schedules a UL (re)transmission for thesame TB. A gNB may assign dedicated resources for retransmission inorder to ensure the TB is delivered within the latency budget. Thisbehavior may be classified as scheduling switching from GF to GBoperation. In this case, a UE may link the received grant with thetransmitted TB in order to understand which TB to be retransmitted incase there are multiple ongoing transmission processes at the UE. In anexample, the UE and gNB may have the same notion of TB counting.

In an example, for the GF operation, the TB counting may not be possibleif a gNB may not detect some TBs due to collisions. In order to make anassociation between a DCI with a TB, there may be several options. Ifthere is no other transmission process at the UE side, the UE maydirectly associate the DCI with a TB which is being transmitted. Ifthere are at least two different TBs, a UE may assume that the DCI isfor a particular TB by applying an implicit linkage assuming one TB istransmitted in one transmission interval. In this case, if the intervalbetween detected UE transmission and a grant is fixed, it may determinewhich TB may be retransmitted. If the timing between a detectedtransmission and a retransmission grant is not preconfigured, anexplicit indication of the retransmitted TB may be carried by the DCI.If a UE detects that a grant for one TB overlaps with transmission ofanother ongoing TB, the UE may assume precedence of the grant comparingto the grant-free retransmissions. If a grant is received for a new TB(e.g. for aperiodic CSI reporting) and overlaps with the GF ULtransmissions, the GF transmissions may be dropped in the resources. Inan example, a prioritization rule whether to transmit a triggered reportor GF data may be introduced depending on priority of the associatedservices. For example, if URLLC services is assumed, then the CSIreporting may be dropped in this example.

A example repetition termination condition may be to use a dedicatedPHICH-like channel for early termination. For this option, the PHICHdefined in LTE may be used as an acknowledge indicator. In LTE, thePHICH for a UE may be determined based on the physical resource block(PRB) and cyclic shift of the DMRS corresponding to the UE's PUSCHtransmission. Similar design principle may be reused Such a PHICH-likechannel may optimize the control channel capacity and system capacity.If a gNB has successfully received a TB, the gNB may obtain thecorresponding information about this transmission, such as the UE ID,the resource used for carrying this transmission, the DMRS used for thistransmission, etc. The physical resources may be shared among multipleUEs that may have unique identifiers (e.g., DMRS) used in the GF radioresource pool. Therefore, even for GF UL transmission, if the gNB hassuccessfully received a TB, a unique PHICH may be determined.

Using a sequence based signal may be used for early termination ofK-repetition. In this case, a sequence based signal may be transmittedto inform the UE to terminate the repetition of transmission. In thiscase, the signal may be transmitted when a gNB successfully decodes aTB. The UE may perform a simple signal detection for the presence orabsence to decide whether to continue the repetitions or not.

A gNB may switch from GF to GB UL transmissions in order to solve a GFradio resource shortage problem. In an example, some UEs whose delayrequirements are not strict may use the GF radio resource to transmitdata. A gNB may measure the status of the GF UL radio resourceutilization based on statistics with respect to resource utilization,load, etc and set up a threshold policy to dynamically balance load orresource utilization of the GF UL radio resource. If the resource usagestatistic of the GF UL radio resource exceeds the predefined threshold,it may be beneficial to switch some UEs from the GF UL radio resource tothe GB UL radio resource, which may decrease the resource collision.

The GF resource pool configuration may not be known to UEs. It may needto be coordinated between different cells for interference coordination.If the GF resource pools are known to UEs, those may be semi-staticallyconfigured by UE-specific RRC signaling or non-UE-specific RRCsignaling. The RRC signaling for GF radio resource configuration mayinclude at least one or more parameters indicating GF time/frequencyradio resources, DMRS parameters, a modulation and coding scheme (MCS)or equivalently a transport block size (TBS), Number of repetitions K,and/or power control parameters.

In an example, in a grant free operation (configured grant of a firsttype) at least one RRC message may configure and activate/initializeradio resources of the configured grant of the first type. A basestation may transmit to a wireless device at least one RRC messagecomprising configuration parameters of the configured grant of the firsttype. The configuration parameters may indicate radio resourceparameters, power control parameters, and/or one or more transmissionparameters.

In an example, a grant-free operation may be implemented using RRCmessages and/or L1 signaling. The need for L1 activation signaling maydepend on actual service types, and the dynamic activation (e.g,activation via L1 activation) may not be supported or may beconfigurable based on service and traffic considerations. A UE may beconfigured with one or more required parameters for UL grant-freetransmission before transmitting via the resource. For thisconfiguration, a wireless device and base station may employ RRCsignaling and L1 signaling. For example, RRC signaling may configurerequired parameters of GF UL transmission to the UE, and L1 signalingmay adjust, modify, update, activate, and/or deactivate theseparameters. The L1 signaling may be a PDCCH, similar to the signalingused for LTE UL semi-persistent scheduling (SPS). Once the GF ULtransmission parameters are configured, a GF UL transmission may beactivated in different ways. In an example, both activation schemes withand without L1 activation signaling may be supported. In an example, forexample RRC based configuration and activation/initialization may besupported. It may be up to a gNB to configure a UE which scheme may needto be used by considering, for example, traffic pattern, latencyrequirements, and other possible aspects. With the L1 activationsignaling, a UE may transmit data with the configured time frequencyradio resource after receiving L1 activation signaling from gNB. If theL1 activation is not configured, UE may start a UL transmission with theconfigured GF radio resource at any moment or in a certain time interval(which may be configured by RRC signaling or pre-defined) once theconfiguration is completed. In an example, if a service that does notrequire high reliability and latency may benefit from reduced signalingoverhead and power consumption, then the L1 activation signaling may bebeneficial in combination with L1 deactivation signaling to controlnetwork resource load and utilization. When the L1 signaling is used,gNB may need to know whether the UE correctly receives it. Anacknowledgement to the L1 signaling may be transmitted from a UE to agNB. For deactivating the activated GF operation, L1 deactivationsignaling may be used for services in order to release resources as fastas possible.

The MCS may be indicated by the UE within the grant-free data. In anexample, in order to reduce the blind decoding of MCS indication, thelimited number of MCS levels may be pre-configured by a gNB, e.g., Kbits may be used to indicate MCS of grant-free data, where K may be assmall as possible. The number of REs used to transmit MCS indication ina resource group may be semi-statically configured. In the GF operation,there may be one common MCS predefined for UEs. GF operation maypredefine a mapping rule between multiple time/frequency resources forUL grant-free transmission and MCSs. In an example, a UE may select anappropriate MCS according to a DL measurement and associatedtime/frequency resources to transmit UL data. A UE may choose a MCSbased on the channel status and increase the resource utilization.

A gNB may configure a GF operation (configured grant of the first type)such that the GF UL transmission is activated/initialized in response toreceiving one or more RRC messages configuring a GF radio resourceconfiguration and transmission parameters.

In example embodiments, two types of configured grants may beimplemented in a wireless network. In a first type of configured grantone or more RRC messages transmitted by a base station may configure andactivate/initialize a grant-free uplink process. In a second type ofconfigured grant one or more RRC messages transmitted by a base stationmay configure at least one semi-persistent scheduling grant. In a secondtype of configured period grant, the base station may transmit L1/L2signaling (e.g. DCI indicating SPS activation) to activate at least oneSPS grant. These two types of uplink transmissions by a wireless deviceis performed without receiving a dynamic grant (e.g. DCI grants). In anexample, in a configured grant of the first type (also called grant-freeprocess) configured uplink radio resources may be shared by multiplewireless devices. In an example, in a configured grant of the secondtype (also called semi-persistent scheduling) configured uplink radioresources may be allocated to one wireless device. In thisspecification, the configured grant of the first type is referred to agrant free transmission, process, and/or operation. The configured grantof the second type is referred to semi-persistent scheduling.

In SPS (configured grant of the second type), a timing offset of anuplink SPS grant depends on L1/L2 signaling activating the SPS grant asshown in FIG. 20 . A base station may transmit at least one RRC messagecomprising SPS RRC parameters comprising SPS periodicity. The basestation may transmit a L1/L2 activation signaling (e.g. a DCI indicatingSPS activation). The wireless device may determine a timing offset ofradio resources of a first SPS grant based on a reception timing of theDCI. The wireless device may transmit one or more transport blocks inthe radio resources. A timing of radio resources of subsequent radioresources are determined based on periodicity.

Determining a timing of the grant-free (configured grant of the firsttype) resources may result in inaccurate timing determination withimplementation of legacy mechanisms for a case that the wireless deviceconfigures and activates/initializes a GF grant (configured grant of thefirst type) in response to receiving an RRC message. With implementationof legacy mechanisms, the GF grant (and/or resource)activated/initialized by the wireless device in response to receivingthe RRC message may be misaligned with the base station's GFconfiguration. There is a need to enhance uplink transmission timedetermination process(es) to improve uplink transmission in a wirelessdevice when the configured grant of the first type is implemented. Inexample embodiments, timing information in the RRC message may provide amore accurate mechanism for determining a timing of the GF grantresource by the wireless device. In an example embodiment, an enhancedGF grant (and/or resource) determination process(es) may be implementedbased on a timing information in the RRC message. For example, the RRCmessage may comprise at least one parameter comprising a timinginformation indicating a timing offset (e.g. slot number e.g. mini-slotnumber), a symbol number, and/or grant-free periodicity. The wirelessdevice may determine a timing of the GF grant resource accurately basedon timing information (e.g. timing offset, symbol number, and/orperiodicity). Example embodiments provide flexibility in configuring theGF resource without a need for L1 signaling transmission of the timinginformation via the RRC message may improve signaling efficiency forconfiguring configuration parameters of the GF grant resource. Anexample grant free process and configuration parameters is shown in FIG.20 .

FIG. 20 is an example diagram as per an aspect of an embodiment of thepresent disclosure. For example, a base station may transmit, to awireless device, a radio resource configuration message comprising oneor more configuration parameters of a configured periodic grant of afirst type (e.g., grant-free resource, grant-free transmission, and/ordynamic-grant-free grant). The one or more configuration parameters mayindicate at least timing offset, a symbol number, and a firstperiodicity. The wireless device may determine a resource of an uplinkgrant of the configured periodic grant of the first type. The wirelessdevice may activate the configured periodic grant in response toreceiving the radio resource configuration message.

An RRC message may activate/initialize a GF grant (and/or resource). Forexample, in response to receiving the RRC message from a base station, awireless device may activate the GF grant (and/or resource). The RRCmessage may comprise one or more GF configuration parameters. The one ormore GF configuration parameters may indicate the GF grant (and/orresource). Activating the GF grant (and/or resource) via the RRC messagemay not require an L1 signaling. Activating the GF grant (and/orresource) via the RRC message may reduce a latency.

In an example, in an operation of a configured grant of a first type(grant free) multiple UEs share the same radio resource pool. A basestation may transmit at least one RRC message to configure andactivate/initialize GF resources. Example embodiments presentimplementation of a time and/or frequency domain configuration for aconfigured grant of the first type. Implementation of the time and/orfrequency domain configuration for grant free operation may not dependon L1/L2 signaling timing. For example, one or RRC parameters mayconfigure transmission timing information in a given frame, e.g. byindicating a timing offset, a symbol number, periodicity, and/orsubframe/TTI pattern. One or more RRC configuration parameters mayindicate the time location (in a frame/subframe) of one or more symbolsallocated to GF resources.

In an example, one or more RRC grant-free parameters may indicate atiming of GF resources in a frame and subframe. For example, grant-freeconfiguration parameters may comprise timing information indicating asubframe number, a slot (e.g. slot, half-slot, mini-slot) number, asymbol number, grant-free periodicity that may configure transmissiontiming of GF resource in a given frame. In an example, the one or moreRRC grant-free parameters may comprise a configuration parameter/indexthat identifies timings of symbols of grant-free resources (e.g. inframes, subframes, and/or slot) of a cell. For example, configurationparameter/index may indicate symbol number 0, 1, or 4 (or othernumbers). An example symbol numbers in a slot is shown in FIG. 2 . TheRRC grant-free configuration parameters may comprise timing offsetindicating, for example, a slot (e.g. slot, half-slot, mini-slot)number. A slot (e.g. slot, half-slot, mini-slot) number may indicate atiming offset in a frame with respect to a position in time (e.g. aknown system frame number, e.g. SFN=0).

In an example embodiment, a wireless device may receive a radio resourcecontrol message comprising one or more configuration parameters of aconfigured periodic grant of a first type. The one or more firstconfiguration parameters indicate: a timing offset and a symbol numberemployed for identifying a resource of an uplink grant of the configuredperiodic grant; a first periodicity of the configured periodic grant,the first periodicity indicating a time interval between two subsequentresources of the configured periodic grant; and one or more demodulationreference signal parameters of the configured grant of the wirelessdevice. In an example, the at least one RRC grant-free configurationparameter may comprise a slot number, a configuration index used foridentifying timings of symbols, and/or grant-free periodicity. Thetimings of symbols (e.g. timing offset, symbol number) of grant-freeresources may be determined based on the RRC grant-free configurationparameters. The wireless device may activate/initialize the configuredperiodic grant in response to the radio resource control message. Thewireless device may determine one or more symbols of the resource of theuplink grant of the configured periodic grant based on the timingoffset, the symbol number, and the first periodicity. The wirelessdevice may transmit, via the resource, one or more transport blocksemploying the one or more demodulation reference signal parameters.

In an example implementation, L1 signaling may comprise a time and/orfrequency offset. In an example, a gNB may inform a UE of shifting aconfigured GF radio resources in time and/or frequency domain bytransmitting L1 signaling with one or more radio resource offset. In anexample, a UE may request a shift of a configured GF radio resources intime and/or frequency domain by transmitting L1 signaling with one ormore radio resource offset. For example, a UE may observe a time ofarrival of URLLC data that is misaligned with a configured GF radioresource in the time domain. In this case, a time shift of theconfigured GF radio resource may be done via the L1 signaling.Similarly, a gNB may request the time or frequency shift, for example,when two UEs configured with different GF radio resources need to beassigned to the same GF radio resource.

In an example implementation, a network may pre-define one or more GFconfigurations, like PRACH configuration index in LTE. The predefined GFconfiguration may comprise a GF configuration ID and at least one of GFradio resource in the time domain, GF radio resource in the frequencydomain (or equivalently a frequency offset), MCS, and/or one or morepower control parameters. When a gNB pre-define large number ofparameters in the GF configuration, there may be less resourcere-allocation flexibility. The network may configure the number ofparameters in the pre-defined GF configuration based on many factorssuch as the service requirements and deployment scenario. When a gNBconfigures a UE with a GF UL transmission, signaling for GFconfiguration, e.g., RRC signaling or L1 signaling, may comprise a GFconfiguration ID indicating a GF configuration among the pre-defined GFconfigurations. The GF configuration ID may be transmitted from a gNB toa UE with one or more GF UL transmission parameters that are not in thepre-defined GF configuration but are employed by the UE to transmit datavia a GF radio resource. In an example, RRC signaling transmitted from agNB to configure a GF transmission for a UE, may comprise a GFconfiguration ID and/or one or more GF transmission parameters that theGF configuration ID may not indicate. The one or more GF transmissionparameters may depend on a format of predefined GF configuration. Forexample, a network may pre-define multiple GF configurations indicatingone or more subframe numbers assigned for a GF UL transmission. A gNBmay inform a UE of one or more remaining GF parameters, such as GFfrequency, MCS, one or more power control parameters, via RRC signalingand/or L1 signaling. In an example, RRC signaling may comprise the GFconfiguration ID selected for the UE and the remaining parameters. In anexample, L1 activation signaling may comprise the GF configuration ID asa indication of activating a GF process with one or more configured GFparameters. In an example, RRC signaling may comprise the GFconfiguration ID indicating time/frequency radio resources, and L1activation signaling may comprise MCS and one or more power controlparameters which may need to be updated more frequently andUE-specifically. FIG. 19 is an example of pre-defined GF configurationscomprising system frame number and subframe number. For example, if a UEis configured with GF config index 3, the GF radio resource is availableevery 7th subframe in the even number of system frame number. In thiscase, the gNB may inform of one or more GF configuration parameters notincluded in the pre-defined GF configuration, e.g., the GF frequency,MCS, one or more power control parameters, via RRC and/or L1 signaling.A gNB may use the GF configuration ID to reconfigure one or more of theGF parameters via RRC signaling and/or L1 signaling. In an example, onceone or more GF parameters are configured, a gNB may transmit amodification L1 signaling with a GF configuration ID different from theone being configured for the GF operation currently. A UE may change oneor more GF parameters based on the new GF configuration ID. DeactivationL1 signaling may comprise a configured GF configuration ID to inform ofreleasing the configured GF radio resources.

In legacy mechanisms for uplink transmissions employing a configuredgrant of a first type (grant free process), a wireless device maytransmit uplink data via the grant free resources. An eNB may not beable to assign a specific logical channel to configured grants of thefirst type. This mechanism may result in inefficiency in uplink datatransmission. Uplink resources of configured grant of the first type maybe employed by data of many logical channels (e.g. low priority data),and uplink resources of configured grant of type one may be congestedand packet collision may increase. There is a need to enhance uplinklogical channel prioritization process for uplink transmission viaconfigured grant of the first type to improve uplink transmissionefficiency. For a case that the wireless device activates/initialize aGF grant (and/or resource) in response to receiving an RRC message froma base station, a first data transmitted via the GF grant (and/orresource) may require higher reliability and/or lower latency versus asecond data transmitted via a dynamic grant, e.g., grant-based (GB) ULtransmission. The wireless device may multiplex data of one or morelogical channels onto one or more packets in a priority order. Exampleembodiments enhances uplink logical channel prioritization process foruplink transmission in configured grants of the first type.

Configuring a GF process (and/or resource) with one or more logicalchannels may provide flexibility for a base station and a wirelessdevice. For example, the wireless device may have data scheduled to betransmitted via the GF resource. The wireless device may multiplex thedata of a first logical channel with a higher (or lower) priority basedon the priority order. Example embodiments configuring a GF process(and/or resource) with one or more logical channels alleviatecongestion. For example, the base station may allocate a grant-freeresource to a plurality of wireless devices. The plurality of wirelessdevices may use the grant-free resource in a contention basis. As morenumber of wireless devices use the resource at the same time, theprobability of collisions increases leading to degraded reliabilityand/or longer latency. Configuring a GF process (and/or resource) withone or more logical channels may place restrictions on the usage ofgrant-free resource. This may result in reducing collisions betweenwireless devices.

A gNB may assign at least one logical channel ID (LCID) and/or logicalchannel group id (LCG ID) to at least one GF process (configured grantof a first type) to recognize the logical channels allowed fortransmission on grant free. Other logical channels may use dynamic orSPS grants (configured grants of the second type) and may not be allowedto use grant free resources. In an example, the RRC signaling maycomprise a LCID (or LCG ID) associated with a GF process. When multipleGF processes are configured, the RRC signaling may be transmitted with aLCID (or LCG ID) associated with a GF configuration, activation,deactivation, and/or modification of a GF process. In an example, a gNBmay assign an LCID (or LCG ID) of a URLLC logical channel for a GFoperation. In an example, if a UE GF resources is not large enough totransmit data of the URLLC buffer, the UE may transmit BSR with theassigned LCID and/or LCG ID in the MAC PDU sub-header.

In an example, the UE may transmit uplink data associated with the atleast one logical channels (or LCGs) configured for GF resources. Thismay reduce uplink transmissions of data of other logical channels (notconfigured for the GF process) in GF resources. This process may reduceGF collisions. In an example, GF resources may be employed fortransmission of one or more uplink MAC CEs. In an example, when there isremaining resources in GF resources after data of the at least onelogical channel (or one LCG) is multiplexed for transmission, the UE maymultiplex and transmit data of other logical channels (or LCGs) and/orMAC CEs in GF resources.

In an example, a wireless device may receive, from a base station, oneor more messages comprising one or more configuration parameters for agrant-free process, wherein the one or more messages comprise at leastone logical channel identifier (or LCG ID) of at least one logicalchannel (or LCG) associated with the grant-free process. The basestation may initiate the grant-free process for transmitting one or moreMAC PDUs. The wireless device may determine, whether data is consideredfor transmission via one or more grant-free resources associated withthe grant-free process, at least based on whether the data is associatedwith the at least one logical channel (or LCG ID). The wireless devicemay transmit, by the wireless device to the base station via the one ormore grant-free resources, the data associated with the at least onelogical channel (or LCG). In an example, the wireless device maydetermine, whether data is considered for transmission via one or moregrant-free resources associated with the grant-free process, furtherbased on a size of the data. The data may be transmitted via one or moreMAC PDUs, wherein a MAC PDU comprises: one or more MAC PDU sub-headers,wherein a sub-header comprises the logical channel identifier (or LCGID); the one or more MAC SDUs, wherein a MAC SDU corresponds to a MACPDU sub-header in the one or more MAC PDU sub-headers.

FIG. 21 is an example diagram as per an aspect of an embodiment of thepresent disclosure. For example, a base station may configure a wirelessdevice with a configured periodic grant of the first type (e.g.,grant-free UL transmission). The base station may transmit, to thewireless device, one or more radio resource control messages. The one ormore radio resource control messages may comprise at least oneparameter. For example, the at least one parameter may indicate whethera configured periodic grant of a first type (e.g., grant-free ULtransmission) can be used for transmission of data of a first logicalchannel. The one or more radio resource control messages may comprise atleast one second parameter. For example, the at least one secondparameter may indicate a resource of an uplink grant of the configuredperiodic grant of the first type. For example, the at least one secondparameter may comprise a symbol number, a timing offset, and a firstperiodicity. The wireless device may determine that the configuredperiodic grant can be used for transmission of data of the first logicalchannel based on the at least one parameter. As a result of determiningthe configured periodic grant can be used for transmission of data ofthe first logical channel, the wireless device may multiplex data of thefirst logical channel onto one or more transport blocks. The wirelessdevice may transmit the one or more transport blocks to the base stationvia the resource of the configured periodic grant of the first type.

In an example, a decision on whether to use the GF or GB UL transmissionmay be based on a size of a data (e.g. relative to a size of GF resourceand/or a threshold) for uplink transmission and/or service requirement(e.g., based on at least one logical channel or LCG associated with GFresource). For example, if a URLLC latency is relaxed for larger packetsize (e.g., larger than 32 bytes), a GB UL transmission may be moreappropriate than a GF UL transmission in terms of reliability with therelaxed latency requirement. For a small size of URLLC packet (e.g.,smaller than 32 bytes), a GF UL transmission may be used with givenlatency and reliability requirements defined for URLLC. A threshold forwhich to decide whether to use a GF UL transmission may be pre-definedor configured by a gNB and/or may be determined based on a size of GFresources. In an example, a UE may consider data of at least one logicalchannel (or LCG) configured for a GF resource. In an example, if databelongs to other logical channels (or other LCGs), the data may not beconsidered to initiate a transmission on GF resource.

Selecting a UL transmission between GF and GB based on a size of datamay result in a situation that a UE may skip an available GF radioresource if a size of that data that the UE wants to transmit is largerthan a threshold. In an example, rather than skipping a GF radioresource, a UE may, via the GF radio resource, transmit BSR indicating asize of the data (e.g. associated with a logical channel id or logicalchannel group id) so that a gNB transmits a UL grant with a right sizeof UL radio resource for the transmission. The size of a data may be asize of a packet. FIG. 22 is an example of a decision mechanism of ULtransmission via a GF radio resource that depends on a pack size. In anexample, a UE may consider data of at least one logical channel (or LCG)configured for a GF resource. In an example, if data belongs to otherlogical channels (or LCGs), the data may not be considered to initiate atransmission on GF resource.

Transmitting a BSR from a wireless device to a base station may provideflexibility in a resource allocation. Transmitting a BSR may provide amore accurate resource allocation. For example, a scheduler (e.g., abase station and/or network) may determine a more accurate amount ofresources for the wireless device. In an example, the wireless devicemay have a large amount of data in its uplink buffers scheduled forgrant-free transmission. It may take long to transmit the data usinggrant-free resources, e.g., it may take long if a size of the grant-freeresources is small comparing with the large amount of data. In thiscase, a wireless device may transmit a BSR to a base station. The basestation may transmit an UL grant for the large amount of data.

Transmitting the BSR via the GF resource may be energy efficient. Awireless device may not need to wait for an UL grant (e.g., for GB ULtransmission) to transmit the BSR. The wireless device may transmit theBSR to inform of a large amount of data in the buffer. The base stationmay transmit an UL grant for the large amount of data. It may takeshorter to transmit the large amount of data based on the UL grant forthe wireless device versus to transmit the large amount of data via GFresources. This may result in reducing a latency and/or saving an energyfor the wireless device.

The BSR may be transmitted in the form of MAC CE with a correspondingsub-header indicating a LCID or LCGID associated with a certain logicalchannel or logical channel group. In an example, a gNB may assign one ormore LCIDs to one or more GF configuration (or equivalently GF radioresources). The BSR that the UE transmits via the GF radio resource maybe a regular BSR or a BSR that comprises a size of the buffer related tothe one or more logical channels (or LCGs) associated with the grantfree resource.

If a gNB successfully receives the BSR, the gNB may transmit one or moreUL grants to a UE in response to the BSR. If a UE receives no uplinkgrant from a gNB, the UE may trigger a scheduling request using PUCCH.

FIG. 23 is an example diagram as per an aspect of an embodiment of thepresent disclosure. For example, a base station may configure a wirelessdevice with a configured periodic grant of the first type (e.g.,grant-free UL transmission). The base station may transmit, to thewireless device, one or more radio resource control messages. The one ormore radio resource control messages may comprise at least oneparameter. For example, the at least one parameter may indicate whethera configured periodic grant of a first type (e.g., grant-free ULtransmission) can be used for transmission of data of a first logicalchannel. The one or more radio resource control messages may comprise atleast one second parameter. For example, the at least one secondparameter may indicate a resource of an uplink grant of the configuredperiodic grant of the first type. For example, the at least one secondparameter may comprise a symbol number, a timing offset, and a firstperiodicity. The wireless device may determine that the configuredperiodic grant can be used for transmission of data of the first logicalchannel based on the at least one parameter. The wireless device maydetermine to multiplex a buffer status report onto at least one packetbased on a size of data of the first logical channel. For example, thewireless device may multiplex the buffer status report onto the at leastone packet in response to determining the size of data being larger thana threshold. The wireless device may transmit the at least one packetvia the resource of the configured periodic grant of the first type. Forexample, the wireless device may multiplex the data onto the at leastone second packet in response to determining the size of data beinglower than or equal to the threshold. The at least one second packet maynot comprise the buffer status report. The wireless device may transmitthe at least one second packet via the resource of the configuredperiodic grant of the first type.

In an example, a wireless device may receive, from a base station, afirst message comprising one or more parameters indicating grant-freeresources and a grant-free uplink transmission. The wireless device mayreceive from the base station, a second message comprising an activationindicator of a grant-free uplink transmission. The wireless device maytransmit to the base station via the grant-free resources, at least onepacket comprising at least one of the following based on a size of datain a logical channel (or a LCG) and a first threshold: a buffer statusreport (BSR) indicating a size of the data and the one or more packets.The first message may further comprise the first threshold. The firstthreshold may be determined based on a size of the grant-free resources.The buffer status report may be a regular BSR. The first message mayindicate that the logical channel (or LCG) is associated with thegrant-free resources. The first message may comprise a logical channelidentifier (LCID) or a LCG ID of the logical channel or LCG associatedwith the grant-free resources.

In the GF UL transmission, there may be a case that a UE may receive noacknowledgement from a gNB in response to a GF UL transmission. In anexample, a gNB may fail to detect a UE ID as well as to decode data,e.g., due to high interference from other UE sharing the same radioresource and/or a bad channel quality of wireless channels. In thiscase, a gNB may not be aware of UE's GF UL transmission and may nottransmit acknowledgment indicating a success of the UL transmission orretransmission of the same or different TB to the UE. The UE mayconsider there is no acknowledgement form the gNB if the UE may fail todetect/decode a gNB's acknowledgement although a gNB transmits apositive or negative acknowledgement. We may call such cases as the GFfailure. When the GF failure occurs, there may be several options forUE, such as triggering a service request procedure, a random accessprocedure, reattempt the initial GF UL transmission, and the UE maydecide which procedure needs to be initiated after the GF failure.

In an example, the UE may initiate one of procedures based on the radioresource allocation and/or latency requirement. One example may be toinitiate the procedure having the earliest available resource after theGF failure. For instance, if the GF failure is determined at subframe n,and the earliest GF, SR, and PRACH radio resource are n+4, n+1, and n+9,respectively, then the UE may initiate the SR procedure which may beinitiated in the next subframe. The UE may consider a periodicity of theradio resource. For example, if GF, SR and PRACH radio resources areavailable every subframe, every two subframes, and every 10 subframes,respectively, the UE may initiate the initial GF UL transmission thathas the shortest periodicity (1 subframe). The UE may consider bothfactors above when choosing a procedure after the GF failure. Forexample, the UE may measure the expected latency and choose the onehaving the shortest one. The expected latency may be calculated based onthe waiting time and minimum latency, wherein the waiting time may bethe time duration from the subframe (or slot or mini-slot) where the UEdetermines the GF failure to the subframe where a radio resource of theselected procedure first available. For example, if the current subframeis n, and the PUCCH for SR is scheduled in n+3 subframes, then thewaiting time may be 3 TTIs. The minimum latency may be the time durationfrom when a procedure is first initiated until receiving anacknowledgement from a gNB in response to the UE's initial transmissionassociated with the procedure. For example, SR, 2-step RACH, and 4-stepRACH may have 4 TTIs, 14 TTIs, and 4 TTIs, respectively, which may beused as the minimum latency of SR, 2-step RACH and 4-step RACH.

In an example, the UE may use a counter counting the number of GFfailures and use the counter to initiate one of procedures. For example,the counter may start from an initial value, e.g., 0, and when GF isfailed, the UE may increase the counter by one. The UE may re-attempt aGF UL transmission until the counter reaches a threshold. If the counterreaches a threshold, UE may stop the GF re-attempt and triggers SR (orBSR). The counter may be reset to 0 if the UE receives a positive ornegative acknowledgement from the gNB. When the UE triggers a SRprocedure, if there is no valid PUCCH for the SR, the UE may trigger arandom access procedure.

In an example, the decision on which procedure needs to be initiated maybe indicated by an RRC parameter. For example, an RRC message comprisingone or more GF configuration parameters may indicate whether a SRprocedure is triggered, a random access procedure is triggered, or noSR/RACH is triggered. For example, an RRC message comprising one or moreGF configuration parameters may indicate whether a SR procedure istriggered or no SR is triggered. For example, an RRC message comprisingone or more GF configuration parameters may indicate whether a randomaccess procedure is triggered, or no RACH is triggered.

If a GF UL transmission is failed, the UE may terminate the GF processand transmit some other MAC/RRC reports indicating the GF failure. Thisreport may be configured by the RRC signaling or configured as a defaultoption.

If a GF UL transmission is failed, the gNB may not be aware that therewas a GF failure until the UE reports it. The gNB may transmit to a UE arequest message to receive information on GF resource usage parameters,e.g. how many times the UE has failed and/or succeeded the GF ULtransmission. Example embodiments employing transmitting the GFstatistics provides a more accurate radio resource allocation. Forexample, the gNB may re-configure UE's nominal power and/or GF radioresources.

FIG. 24 is an example of GF failure report procedure. In an example, thegNB may initiate the procedure by transmitting a UE information requestmessage, referred to as UEInformationRequest, e.g. via RRC. The gNB mayinitiate this procedure when the security is activated successfully. TheUE transmits a UE information response message, referred to asUEInformationResponse, in response to the UE information requestmessage.

The UEInformationRequest may comprise a parameter, referred to asGF-ReportReq, indicating whether the UE needs to include GF statistics(e.g. failure, success) in the UE information response message, a timeduration/period, and/or a type of GF required statistics. TheUEInformationResponse may comprise at least one of following: aparameter indicating a number of transmission attempts via grant-freeresources; a parameter indicating a number of times that the wirelessdevice receives no acknowledgement from the base station in response tothe transmission attempts via grant-free resources; a parameterindicating a number of times that the wireless device receives apositive or negative acknowledgement from the base station in responseto the transmission attempts via grant-free resources; a parameterrelated to a data size for grant free transmission; a parameterindicating a measurement duration; a parameter indicating an indicatorwhether the wireless device detects one or more collisions when thewireless device receives no acknowledgement from the base station inresponse to a GF transmission attempt; and a parameter indicating anumber of collisions detected by the wireless device when the wirelessdevice receives no acknowledgement from the base station in response toa GF transmission attempt, and/or other parameters related to GFtransmission.

In an example, a wireless device may receive, from a base station, afirst message configured to request a grant-free transmission stateinformation. The wireless device may transmit to the base station inresponse to the first message, a second message comprising at least oneof following: a parameter indicating a number of transmission attemptsvia grant-free resources, a parameter indicating a number of times thatthe wireless device receives no acknowledgement from the base station inresponse to the transmission attempts via grant-free resources, aparameter indicating a number of times that the wireless device receivesa positive or negative acknowledgement from the base station in responseto the transmission attempts via grant-free resources, a parameterindicating a measurement duration, a parameter indicating an indicatorwhether the wireless device detects one or more collisions when thewireless device receives no acknowledgement from the base station inresponse to a GF transmission attempt, and a parameter indicating anumber of collisions detected by the wireless device when the wirelessdevice receives no acknowledgement from the base station in response toa GF transmission attempt. The first message may further comprise agrant-free resource configuration index, grant-free RNTI, or a parameteridentifying the grant-free process. The second message may furthercomprise the grant-free resource configuration index, grant-free RNTI,or a parameter identifying the grant-free process. One or more elementsof the second message may be associated with the grant-free resourceconfiguration index, grant-free RNTI, or a parameter identifying thegrant-free process.

FIG. 25 is an example diagram as per an aspect of an embodiment of thepresent disclosure. For example, a base station may transmit, to awireless device, at least one first message. The at least one firstmessage may indicate a resource of a configured periodic grant of thefirst type (e.g., grant-free UL transmission). The at least one firstmessage may activate the configured periodic grant of the first type.The base station may transmit a second message. For example, the secondmessage may be a UE information request. The second message may be arequest of transmitting statistics of one or more UL transmissions viathe resource of the configured periodic grant of the first type. Thestatistics may indicate or comprise at least one of following: a firstnumber of UL transmission via the resource of the configured periodicgrant of the first type, a second number of times that the wirelessdevice receives no acknowledgement from the base station in response tothe first number of UL transmissions, a third number of times that thewireless device receives a positive or negative acknowledgement from thebase station in response to the first number of UL transmissions, and ameasurement duration. The wireless device may transmit a third messageto the base station in response to receiving the second message. Thethird message may be a UE information response. For example, the thirdmessage may comprise one or more parameters indicating the statistics.

A gNB may initiate a discontinuous reception (DRX) procedure to reducethe UE's power consumption for a UE. The gNB may configure one or moreDRX configuration parameters via RRC, e.g., RRCConnectionReconfiguration or RRC Connection Setup message. The one ormore DRX configuration parameters may comprise Drx-RetransmissionTimer,HARQ RTT timer, Drx-ULRetransmissionTimer, and/or UL HARQ RTT timer,wherein Drx-RetransmissionTimer may indicate the maximum number ofconsecutive PDCCH-subframe(s) until a DL retransmission is received,Drx-ULRetransmissionTimer may indicate the maximum number of consecutivePDCCH-subframe(s) until a grant for UL retransmission is received, HARQRTT Timer may indicate the minimum amount of subframe(s) before a DLassignment for HARQ retransmission is expected by the MAC entity, and ULHARQ RTT Timer may indicate the minimum amount of subframe(s) before aUL HARQ retransmission grant is expected by the MAC entity.

The gNB may configure the one or more DRX configuration parameters forone or more service types (e.g., URLLC). For example, aDrx-ULRetransmissionTimer may be configured for URLLC such that a UE mayhave the Drx-ULRetransmissionTimer for URLLC shorter than the one forother services to achieve a strict requirement (latency). In an example,HARQ RTT timer, Drx-RetransmissionTimer and/or UL HARQ RTT timer may beconfigured for one or more service types, e.g., URLLC. In an example, aservice type may be identified by a logical channel identifier.

The gNB may configure the one or more DRX configuration parameters forone or more logical channel. In an example, theDrx-ULRetransmissionTimer and/or UL HARQ RTT may be configured for alogical channel associated with URLLC so that a UE may have a differentDrx-ULRetransmissionTimer for URLLC.

The gNB may configure the one or more DRX configuration parameters,e.g., Drx-ULRetransmissionTimer, UL HARQ RTT timer, for a GFconfiguration.

When a UE is configured with a DRX mode and transmits data to a gNB viathe GF UL transmission, the UE may start a UL HARQ RTT timer in responseto the GF UL transmission. If the UL HARQ RTT timer expires, the UE maystart a Drx-ULRetransmissionTimer and start to monitor PDCCH to checkwhether there is a positive or negative acknowledgement corresponding tothe GF UL transmission from the gNB. In this case, there may be one ormore available UL resources for the UE to transmit data prior to theexpiration of the Drx-ULRetransmissionTimer. In this case, depending onwhether the UE use the one or more available UL resources for ULtransmission, the Drx-ULRetransmissionTimer and/or UL HARQ RTT timer maybe managed in different ways.

In an example, when a Drx-ULRetransmissionTimer is running in a TTI andthere is a GF UL resource (or any usable resource in term of size)available in the TTI, the UE may stop the Drx-ULRetransmissionTimer andthe UE re-attempts another UL transmission. The UE may start the UL HARQRTT timer in response to the re-attempt of another UL transmission.

In an example, when a Drx-ULRetransmissionTimer is running in a TTI andthere is a GF UL resource (or any usable resource in term of size)available in the TTI, the UE may not use the uplink resource for GFtransmission. When the Drx-ULRetransmissionTimer expires, the UE mayre-attempt another GF UL transmission for transmitting the same TB in afirst available uplink GF resource and may start UL HARQ RTT timer.

In an example, a wireless device may receive, from a base station, afirst message comprising a drx uplink retransmission timer. The wirelessdevice may transmit to the base station a first data via a firstgrant-free radio resource. The wireless device may start the drx uplinkretransmission timer. The wireless device may transmit to the basestation, a second data via a second grant-free radio resource, whereinthe wireless device stops the drx uplink retransmission timer. Thewireless device may employ the drx uplink retransmission timer todetermine an active time duration of a discontinuous reception. Thefirst data may be the second data.

FIG. 26 is an example diagram of a first timer (e.g., a HARQ RTT timer)and a second timer (e.g., a drx uplink retransmission timer). A basestation may transmit, to a wireless device, at least one RRC messagecomprising one or more configuration parameters of a configured periodicgrant of a first type (e.g., GF UL transmission). The one or moreconfiguration parameters may indicate resources of the configuredperiodic grant of the first type. The one or more configurationparameters may indicate a first value of the first timer and a secondvalue of the second timer. An DRX operation may be triggered in thewireless device. The wireless device may have data to transmit duringthe DRX operation. The wireless device may transmit the data via theresources of the configured periodic grant of the first type. Forexample, the wireless device may transmit the data via the resources ofthe configured periodic grant of the first type in response to the dataof a logical channel being detected as associated with the configuredperiodic grant. The wireless device may start the first timer inresponse to transmitting the data via the resources of the configuredperiodic grant of the first type. In response to expiry of the firsttimer, the wireless device may start the second timer. The wirelessdevice may start to monitor a downlink control channel in response tostarting the second timer. The wireless device may have second data totransmit via the resources of the configured periodic grant of the firsttype when the second timer is running. The wireless device may stop thesecond timer in response to transmitting the second data via theresources of the configured periodic grant of the first type. Thewireless device may start the first timer in response to transmittingthe second data.

In an example, a wireless device may receive, from a base station, afirst message comprising one or more drx uplink retransmission timers,wherein the first message further comprises one or more logical channel(or service or bearer) identifiers of one or more service typesassociated with at least one of one or more drx uplink retransmissiontimers. The wireless device may transmit to the base station, at leastone transport block via a radio resource. The wireless device may startone of the one or more drx uplink retransmission timers, wherein the oneof the one or more drx uplink retransmission timers is determined atleast based on a service type of the at least one transport block andone or more elements of the first message. The service type of the atleast one transport block may comprise at least one of the following:ultra-reliable low latency communications, enhanced mobile broadband,and massive machine-type communications. The one of the one or more drxuplink retransmission timers may be determined based on an uplinkscheduling type, wherein the uplink scheduling type comprises at leastone of the following: grant-free uplink scheduling, grant-based uplinkscheduling, and semi-persistent scheduling. The wireless device mayemploy at least one of the one or more drx uplink retransmission timersto determine an active time duration of a discontinuous reception.

In an example, for the purposes of the present disclosures, thefollowing terms and definitions may apply. Active Time may indicate timerelated to DRX operation during which the MAC entity monitors the PDCCH.mac-ContentionResolutionTimer may indicate the number of consecutivesubframe(s) during which the MAC entity may monitor the PDCCH after Msg3is transmitted. DRX Cycle may indicate the periodic repetition of the OnDuration followed by a possible period of inactivity.drx-InactivityTimer may indicate, except for NB-IoT, the number ofconsecutive PDCCH-subframe(s) after the subframe in which a PDCCHindicates an initial UL, DL or SL user data transmission for this MACentity. For NB-IoT, it specifies the number of consecutivePDCCH-subframe(s) after the subframe in which the HARQ RTT timer or ULHARQ RTT timer expires. drx-RetransmissionTimer may indicate the maximumnumber of consecutive PDCCH-subframe(s) until a DL retransmission isreceived. drxShortCycleTimer may indicate the number of consecutivesubframe(s) the MAC entity may follow the Short DRX cycle.drxStartOffset may indicate the subframe where the DRX Cycle starts.drx-ULRetransmissionTimer may indicate the maximum number of consecutivePDCCH-subframe(s) until a grant for UL retransmission is received.

HARQ information may indicate information for DL-SCH or for UL-SCHtransmissions comprise at least one of New Data Indicator (NDI) andTransport Block (TB) size. For DL-SCH transmissions and for asynchronousUL HARQ, the HARQ information also includes HARQ process ID, except forUEs in NB-IoT for which this information is not present. For UL-SCHtransmission the HARQ information also includes Redundancy Version (RV).In case of spatial multiplexing on DL-SCH the HARQ information comprisesa set of NDI and TB size for a transport block. HARQ information forSL-SCH and SL-DCH transmissions comprises of TB size.

HARQ RTT Timer may indicate the minimum amount of subframe(s) before aDL assignment for HARQ retransmission is expected by the MAC entity.Msg3 may indicate a message transmitted on UL-SCH containing a C-RNTIMAC CE or CCCH SDU, submitted from upper layer and associated with theUE Contention Resolution Identity, as part of a random access procedure.NB-IoT may allow access to network services via E-UTRA with a channelbandwidth limited to 200 kHz. NB-IoT UE may indicate a UE that usesNB-IoT. onDurationTimer may indicate the number of consecutivePDCCH-subframe(s) at the beginning of a DRX Cycle. PDCCH may indicatethe PDCCH, EPDCCH (in subframes when configured), MPDCCH, for an RN withR-PDCCH configured and not suspended, to the R-PDCCH or, for NB-IoT tothe NPDCCH. PDCCH period (pp) may indicate the interval between thestart of two consecutive PDCCH occasions and depends on the currentlyused PDCCH search space. A PDCCH occasion may be the start of a searchspace and is defined by subframe k0. The calculation of number ofPDCCH-subframes for the timer configured in units of a PDCCH period maybe done by multiplying the number of PDCCH periods withnpdcch-NumRepetitions-RA when the UE uses the common search space or bynpdcch-NumRepetitions when the UE uses the UE specific search space. Thecalculation of number of subframes for the timer configured in units ofa PDCCH period may be done by multiplying the number of PDCCH periodswith duration between two consecutive PDCCH occasions.

PDCCH-subframe may indicate a subframe with PDCCH. Some example forPDCCH subframe are presented here. This may represent the union overPDCCH-subframes for serving cells excluding cells configured with crosscarrier scheduling for both uplink and downlink; except if the UE is notcapable of simultaneous reception and transmission in the aggregatedcells where this instead represents the PDCCH-subframes of the SpCell.For FDD serving cells, all subframes may represent PDCCH-subframes. ForTDD serving cells, all downlink subframes and subframes including DwPTSof the TDD UL/DL configuration indicated by tdd-Config of the cell mayrepresent PDCCH-subframes. For serving cells operating according toFrame structure Type 3, all subframes may represent PDCCH-subframes. ForRNs with an RN subframe configuration configured and not suspended, inits communication with the E-UTRAN, all downlink subframes configuredfor RN communication with the E-UTRAN may represent PDCCH-subframes. ForSC-PTM reception on an FDD cell, all subframes except MBSFN subframesmay represent PDCCH-subframes. For SC-PTM reception on a TDD cell, alldownlink subframes and subframes including DwPTS of the TDD UL/DLconfiguration indicated by tdd-Config of the cell except MBSFN subframesmay represent PDCCH-subframes.

PDSCH may indicate PDSCH or for NB-IoT to NPDSCH. PRACH may indicatePRACH or for NB-IoT to NPRACH. PRACH Resource Index may indicate theindex of a PRACH within a system frame. Primary Timing Advance Group mayindicate a Timing Advance Group containing the SpCell. PUCCH SCell mayindicate an SCell configured with PUCCH. PUSCH may indicate PUSCH or forNB-IoT to NPUSCH. ra-PRACH-MaskIndex may define in which PRACHs within asystem frame the MAC entity may transmit a Random Access Preamble.RA-RNTI may indicate the Random Access RNTI is used on the PDCCH whenRandom Access Response messages are transmitted. It may unambiguouslyidentifie which time-frequency resource was utilized by the MAC entityto transmit the Random Access preamble.

SC Period may indicate a sidelink Control period, the time periodcomprising of transmission of SCI and its corresponding data. SCI mayindicatet the Sidelink Control Information contains the sidelinkscheduling information such as resource block assignment, modulation andcoding scheme, Group Destination ID (e.g., for sidelink communication)and PPPP(ProSe Per-Packet. Priority for V2X sidelink communication).

Secondary Timing Advance Group may indicate Timing Advance Group notcontaining the SpCell. A Secondary Timing Advance Group may contain atleast one Serving Cell with an UL configured. Serving Cell may indicatea Primary or a Secondary Cell.

Sidelink may indicate UE to UE interface for sidelink communication,sidelink discovery and V2X sidelink communication. The sidelinkcorresponds to the PC5 interface for sidelink communication and sidelinkdiscovery, and for V2X sidelink communication. Sidelink communicationmay indicate AS functionality enabling ProSe Direct Communicationbetween two or more nearby UEs, using E-UTRA technology but nottraversing any network node. Sidelink Discovery Gap for Reception mayindicate a time period during which the UE does not receive any channelsin DL from any serving cell, except during random access procedure.Sidelink Discovery Gap for Transmission may indicate a time periodduring which the UE prioritizes transmission of sidelink discovery andassociated procedures e.g. re-tuning and synchronisation overtransmission of channels in UL, if they occur in the same subframe,except during random access procedure.

Special Cell may indicate, for Dual Connectivity operation, the PCell ofthe MCG or the PSCell of the SCG, otherwise the term Special Cell refersto the PCell. Timing Advance Group may indicate a group of Serving Cellsthat is configured by RRC and that, for the cells with an UL configured,using the same timing reference cell and the same Timing Advance value.

UL HARQ RTT Timer may indicate the minimum amount of subframe(s) beforea UL HARQ retransmission grant is expected by the MAC entity. A timermay be running once it is started, until it is stopped or until itexpires; otherwise it may not be running. A timer may be started if itis not running or restarted if it is running. A Timer may be started orrestarted from its initial value.

In an example, the MAC entity may be configured by RRC with a DRXfunctionality that controls the UE's PDCCH monitoring activity for theMAC entity's C-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, Semi-PersistentScheduling C-RNTI (if configured), eIMTA-RNTI (if configured), SL-RNTI(if configured), SL-V-RNTI (if configured), CC-RNTI (if configured), andSRS-TPC-RNTI (if configured). When in RRC_CONNECTED, if DRX isconfigured, the MAC entity may be allowed to monitor the PDCCHdiscontinuously using the DRX operation specified in this disclosure asan example embodiment; otherwise the MAC entity may monitor the PDCCHcontinuously. When using DRX operation, the MAC entity may also monitorPDCCH according to requirements found in other disclosure as an exampleembodiments of this specification. RRC may control DRX operation byconfiguring the timers onDurationTimer, drx-InactivityTimer,drx-RetransmissionTimer (one per DL HARQ process except for thebroadcast process), drx-ULRetransmissionTimer (one per asynchronous ULHARQ process), the longDRX-Cycle, the value of the drxStartOffset andoptionally the drxShortCycleTimer and shortDRX-Cycle. A HARQ RTT timerper DL HARQ process (except for the broadcast process) and UL HARQ RTTTimer per asynchronous UL HARQ process may be also defined.

When a DRX cycle is configured, the Active Time may include the timewhile: onDurationTimer or drx-InactivityTimer or drx-RetransmissionTimeror drx-ULRetransmissionTimer or mac-ContentionResolutionTimer isrunning; or a Scheduling Request is sent on PUCCH and is pending; or anuplink grant for a pending HARQ retransmission may occur and there isdata in the corresponding HARQ buffer for synchronous HARQ process; or aPDCCH indicating a new transmission addressed to the C-RNTI of the MACentity has not been received after successful reception of a RandomAccess Response for the preamble not selected by the MAC entity.

An example DRX process is described here. When DRX is configured, theMAC entity may for a subframe: if a HARQ RTT Timer expires in thissubframe and if the data of the corresponding HARQ process was notsuccessfully decoded, may start the drx-RetransmissionTimer for thecorresponding HARQ process; if a HARQ RTT Timer expires in this subframeand if NB-IoT, may start or restart the drx-InactivityTimer. When DRX isconfigured, the MAC entity may for a subframe start thedrx-ULRetransmissionTimer for the corresponding HARQ process, e.g., ifan UL HARQ RTT Timer expires in this subframe. The MAC entity may for asubframe start or restart the drx-InactivityTimer, e.g., if NB-IoT.

When DRX is configured, the MAC entity may for a subframe stoponDurationTimer and stop drx-InactivityTimer, for example, if a DRXCommand MAC control element or a Long DRX Command MAC control element isreceived. When DRX is configured, the MAC entity may for a subframestart or restart drxShortCycleTimer and use the Short DRX Cycle, e.g.,if drx-InactivityTimer expires or a DRX Command MAC control element isreceived in the subframe and if the Short DRX cycle is configured. Forexample, if drx-InactivityTimer expires or a DRX Command MAC controlelement is received in the subframe and if the Short DRX cycle is notconfigured the MAC entity may use the Long DRX cycle.

In an example, the MAC entity may use the Long DRX cycle, e.g., ifdrxShortCycleTimer expires in this subframe and/or may stopdrxShortCycleTimer; and use the Long DRX cycle, e.g., if a Long DRXCommand MAC control element is received. The MAC entity may startonDurationTime at least one of following conditions satisfied: If theShort DRX Cycle is used and [(SFN*10)+subframe number] modulo(shortDRX-Cycle)=(drxStartOffset) modulo (shortDRX-Cycle); if the LongDRX Cycle is used and [(SFN*10)+subframe number] modulo(longDRX-Cycle)=drxStartOffset; if NB-IoT; if there is at least one HARQprocess for which neither HARQ RTT Timer nor UL HARQ RTT Timer isrunning.

An example process for Active Time is described here. During the ActiveTime, the MAC entity may monitor the PDCCH for a PDCCH-subframe if atleast one of conditions satisfied: if the subframe is not required foruplink transmission for half-duplex FDD UE operation; if the subframe isnot a half-duplex guard subframe and if the subframe is not part of aconfigured measurement gap; if the subframe is not part of a configuredSidelink Discovery Gap for Reception; if the UE is NB-IoT; if thesubframe is not required for uplink transmission or downlink receptionother than on PDCCH; if the subframe is a downlink subframe indicated bya valid eIMTA L1 signalling for at least one serving cell not configuredwith schedulingCellId and if the subframe is not part of a configuredmeasurement gap and if the subframe is not part of a configured SidelinkDiscovery Gap for Reception for a subframe other than a PDCCH-subframeand for a UE capable of simultaneous reception and transmission in theaggregated cells; or if the subframe is a downlink subframe indicated bya valid eIMTA L1 signalling for the SpCell and if the subframe is notpart of a configured measurement gap and if the subframe is not part ofa configured Sidelink Discovery Gap for Reception for a subframe otherthan a PDCCH-subframe and for a UE not capable of simultaneous receptionand transmission in the aggregated cells.

In an example, the MAC entity may start the HARQ RTT Timer for thecorresponding HARQ process in the subframe containing the lastrepetition of the corresponding PDSCH reception if the PDCCH indicates aDL transmission or if a DL assignment has been configured for thissubframe and/or if the UE is an NB-IoT UE, a BL UE or a UE in enhancedcoverage.

In an example, the MAC entity may start the HARQ RTT Timer for thecorresponding HARQ process, e.g., if the PDCCH indicates a DLtransmission or if a DL assignment has been configured for this subframeand if the UE is not an NB-IoT UE, a BL UE or a UE in enhanced coverage.In an example, the MAC entity may stop the drx-RetransmissionTimer forthe corresponding HARQ process if the PDCCH indicates a DL transmissionor if a DL assignment has been configured for this subframe. For anNB-IoT, in an example, the MAC entity stop drx-ULRetransmissionTimer forUL HARQ processes if the PDCCH indicates a DL transmission or if a DLassignment has been configured for this subframe.

In an example, the MAC entity may start the UL HARQ RTT Timer for thecorresponding HARQ process in the subframe containing the lastrepetition of the corresponding PUSCH transmission and stop thedrx-ULRetransmissionTimer for the corresponding HARQ process, e.g., ifthe PDCCH indicates an UL transmission for an asynchronous HARQ processor if an UL grant has been configured for an asynchronous HARQ processfor this subframe.

In an example, the MAC entity may, except for a NB-IoT UE configuredwith a single DL and UL HARQ process, start or restartdrx-InactivityTimer, e.g., if the PDCCH indicates a new transmission(DL, UL or SL). In an example, the MAC entity may stop onDurationTimerif the PDCCH indicates a transmission (DL, UL) for a NB-IoT UE and/or ifthe NB-IoT UE is configured with a single DL and UL HARQ process.

In current subframe n, if the MAC entity may not be in Active Timeconsidering grants/assignments/DRX Command MAC control elements/Long DRXCommand MAC control elements received and Scheduling Request sent untiland including subframe n-5 when evaluating DRX Active Time conditions asspecified in this disclosure as an example embodiment, type-O-triggeredSRS may not be reported.

If CQI masking (cqi-Mask) is setup by upper layers: in current subframen, if onDurationTimer may not be running consideringgrants/assignments/DRX Command MAC control elements/Long DRX Command MACcontrol elements received until and including subframe n-5 whenevaluating DRX Active Time conditions as specified in this disclosure asan example embodiment, CQI/PMI/RI/PTI/CRI on PUCCH may not be reported.If CQI masking (cqi-Mask) is not setup by upper layers, in currentsubframe n, if the MAC entity may not be in Active Time consideringgrants/assignments/DRX Command MAC control elements/Long DRX Command MACcontrol elements received and Scheduling Request sent until andincluding subframe n-5 when evaluating DRX Active Time conditions asspecified in this disclosure as an example embodiment,CQI/PMI/RI/PTI/CRI on PUCCH may not be reported.

Regardless of whether the MAC entity is monitoring PDCCH or not, the MACentity may receive and transmit HARQ feedback and transmitstype-1-triggered SRS when such may be expected. The MAC entity maymonitor PDCCH addressed to CC-RNTI for a PUSCH trigger B on thecorresponding SCell even if the MAC entity is not in Active Time whensuch may be expected.

When the BL UE or the UE in enhanced coverage or NB-IoT UE receivesPDCCH, the UE may execute the corresponding action specified in thisdisclosure as an example embodiment in the subframe following thesubframe containing the last repetition of the PDCCH reception wheresuch subframe may be determined by the starting subframe and the DCIsubframe repetition number field in the PDCCH, unless explicitly statedotherwise. In an example, the same Active Time may apply to activatedserving cell(s).

In case of downlink spatial multiplexing, if a TB is received while theHARQ RTT Timer is running and the previous transmission of the same TBwas received at least N subframes before the current subframe (where Ncorresponds to the HARQ RTT Timer), the MAC entity may process it andrestart the HARQ RTT Timer.

The MAC entity may not consider PUSCH trigger B to be an indication of anew transmission. For NB-IoT DL and UL transmissions may not bescheduled in parallel, i.e. if a DL transmission has been scheduled anUL transmission may not be scheduled until HARQ RTT Timer of the DL HARQprocess has expired (and vice versa).

A closed-loop power control may be employed for GF transmission. datatransmitted via the GF resource may have requirements (e.g., in terms ofreliability and/or latency) different from other data transmitted viadynamic grants and/or SPS grants. For example, the transmission of datavia GF resource by employing a legacy power control mechanism may notmeet the requirements. There is a need to enhance uplink transmissionpower determination process(es) to improve uplink transmission. In anexample embodiment, a new uplink transmission power determinationprocess may be implemented when one or more GF transmissions areconfigured via RRC signaling. The new uplink transmission powerdetermination process may have one or more power control parameters forthe GF transmission, e.g., GF-specific power offset, GF-specific initialpower, GF-specific ramp-up power, etc employed for transmission on GFresources. An example embodiment may determine uplink transmission powerof the one or more GF transmissions to improve uplink power control.Using an GF-specific power offset and/or GF-specific initial power foruplink transmission power calculation may provide a more accuratemeasurement for the calculation versus without using a GF-specific poweroffset and/or GF-specific initial power. Example embodiments provide amore efficient and accurate power control. In an example embodiment, abase station may transmit one or more messages (e.g. RRC messages)comprising a power offset value and/or initial power received targetpower for the GF transmission. The example signaling mechanism mayprovide flexibility in configuring different transmission powers for GFtransmission, GB (e.g., dynamic grant based) transmission, and/orsemi-persistent scheduling based transmissions.

The initial received target power at a gNB may be configuredsemi-statically. The most recent uplink transmit power control commandmay be re-used for GF transmission. In an example, A group common PDCCH,e.g., DCI format 3/3A in LTE, may be employed to inform a UE of atransmit power control (TPC) order for the closed-loop power control ofthe GF UL transmission. A gNB may configure the different initialreceived target powers for different scheduling types via RRC. In anexample, the gNB may configure one or more GF transmission parametersvia RRC signaling comprising an initial received target power for the GFtransmission. The initial received target power for the GF transmissionmay be configured in different ways. In an example, the initial receivedtarget power for the GF transmission may be configured using RRCsignaling. The RRC signaling may comprise a GF-specific initial receivedtarget power parameter (IE) different from other grant type of grants,e.g., semi-persistent grant, dynamic scheduled grant. In an example, theinitial received target power for the GF transmission may be configuredin terms of a GF-specific power offset. The UE may set the initialreceived target power for the GF transmission based on the configuredGF-specific power offset and an initial received target power ofsemi-persistent grant type or dynamic scheduled grant. For example, theinitial received target power for the GF transmission may be the sum ofthe configured GF-specific power offset and the initial received targetpower of semi-persistent grant type.

FIG. 27 is an example of uplink power control for a GF (e.g., configuredperiodic grant of a first type) transmission. A base station maytransmit, to a wireless device, an RRC message comprising one or more GFconfiguration parameters. The one or more GF configuration parametersmay indicate at least: a first power offset value, timing offset, asymbol number, and a first periodicity. The first power offset value mayby GF-specific power offset. The wireless device may activate a grant(e.g., configured periodic grant of the first type) of the GFtransmission in response to receiving the RRC message. The wirelessdevice may determine a first UL transmission power via a resource of angrant of the GF transmission. The first UL transmission power maycomprise the first power offset value.

In the GF UL transmission, if the GF failure occurs, e.g., a UE receivesno acknowledgement from a gNB, the UE may re-attempt the GF ULtransmission with a ramp-up power. The power ramping step for there-attempt of the GF UL transmission may be constant. In an example, aconstant power offset value may be pre-defined or configured via RRC forthe GF failure. An RRC message may comprise GF configuration parameterscomprising a power ramp up value and/or a maximum counter value. A UEmay increment the transmit power accumulated in a GF re-attempt untilthe UE reaches a maximum allowable transmission power. For example, theUE may employ a counter counting the total number of GF reattempts. Ifthe ramping power step is pre-defined or configured via RRC for the GFfailure, the UE may set the ramp-up power to n*(ramping power step) forthe n-the GF re-attempt. The UE may increment the counter if the UE doesnot receive an acknowledgement from the gNB in response to a GF uplinktransmission; and may reset the counter to an initial value, e.g., 0, ifthe UE receives a positive or negative acknowledgement from the gNB inresponse to a GF uplink transmission.

In an example, a wireless device may receive, from a base station, afirst message comprising one or more configuration parameters of agrant-free radio resource parameter and a GF uplink transmissionparameter, wherein the first message comprises at least one grant-freepower parameter associated with GF transmission. The wireless device maytransmit to the base station via the grant-free resource, at least onetransport block (TB) with a first transmission power, wherein the firsttransmission power is based on: at least one grant-free power parameterassociated with GF transmission and at least one uplink power controlcommand received from the base station. The at least one power parametermay comprise: the configured initial received target power and theoffset value depending on a type of uplink scheduling. The firsttransmission power may be further based on a ramp-up power value. Thetype of uplink scheduling may comprise at least one of the followings:Grant-free uplink scheduling, Grant-based uplink scheduling, andSemi-persistent scheduling. The first message may further comprise afirst indicator indicating whether the first message or a second messageinitiates a GF transmission. The first message may further comprise atiming information indicating when the wireless device initiates the GFtransmission. The wireless device may receive the second message if thefirst indicator is configured to initiate the GF transmission by thesecond message. The wireless device may initiate the GF transmissionbased on at least one of the first message and the second message. Thefirst transmission power may further comprise a pathloss value estimatedbased on one or more measurement signals. The ramp-up power value may bedetermined based on a first counter indicating a number of times thatthe wireless device does not receive an acknowledgement from the basestation in response to a GF uplink transmission. The wireless device mayincrement the first counter if the wireless device does not receive anacknowledgement from the base station in response to a GF uplinktransmission and reset the first counter to an initial value if thewireless device receives an acknowledgement from the base station inresponse to a GF uplink transmission.

In an example, when GF traffic is transmitted or re-transmitted using adynamic grant (PDCCH uplink grant), a transmission power for GF packetmay use transmission power calculation of a dynamic packet. In anexample, when GF traffic is transmitted or re-transmitted using adynamic grant (PDCCH uplink grant), a transmission power for GF packetmay use transmission power calculation of a GF power parameters.

Example power control mechanism is described here. Some detailedparameters are provided in examples. The basic processes may beimplemented in technologies such as LTE, New Radio, and/or othertechnologies. A radio technology may have its own specific parameters.Example embodiments describe a method for implementing power controlmechanism. Other example embodiments of the disclosure using differentparameters may be implemented. Some example embodiments enhance physicallayer power control mechanisms when some layer 2 parameters are takeninto account.

In an example embodiment, downlink power control may determine theEnergy Per Resource Element (EPRE). The term resource element energy maydenote the energy prior to CP insertion. The term resource elementenergy may denote the average energy taken over constellation points forthe modulation scheme applied. Uplink power control determines theaverage power over a SC-FDMA symbol in which the physical channel may betransmitted. Uplink power control may control the transmit power of thedifferent uplink physical channels. In an example, if a UE is configuredwith a LAA SCell for uplink transmissions, the UE may apply theprocedures described for PUSCH and SRS in this clause assuming framestructure type 1 for the LAA SCell unless stated otherwise.

In an example, for PUSCH, the transmit power {circumflex over(P)}_(PUSCH,c)(i), may be first scaled by the ratio of the number ofantennas ports with a non-zero PUSCH transmission to the number ofconfigured antenna ports for the transmission scheme. The resultingscaled power may be then split equally across the antenna ports on whichthe non-zero PUSCH is transmitted. For PUCCH or SRS, the transmit power{circumflex over (P)}_(PUCCH)(i), or {circumflex over (P)}_(SRS,c)(i)may be split equally across the configured antenna ports for PUCCH orSRS. {circumflex over (P)}_(SRS,c)(i) may be the linear value of{circumflex over (P)}_(SRS,c)(i). A cell wide overload indicator (OI)and a High Interference Indicator (HII) to control UL interference maybe parameters in LTE technology.

In an example, for a serving cell with frame structure type 1, a UE isnot expected to be configured with UplinkPowerControlDedicated-v12x0. Inan example, if the UE is configured with a SCG, the UE may apply theprocedures described in this clause for both MCG and SCG. For example,when the procedures are applied for MCG, the terms ‘secondary cell’,‘secondary cells’, ‘serving cell’, ‘serving cells’ in this clause referto secondary cell, secondary cells, serving cell, serving cellsbelonging to the MCG respectively. For example, when the procedures areapplied for SCG, the terms ‘secondary cell’, ‘secondary cells’, ‘servingcell’, ‘serving cells’ in this clause refer to secondary cell, secondarycells (not including PSCell), serving cell, serving cells belonging tothe SCG respectively. The term ‘primary cell’ in this clause refers tothe PSCell of the SCG.

In an example, if the UE is configured with a PUCCH-SCell, the UE mayapply the procedures described in this clause for both primary PUCCHgroup and secondary PUCCH group. For example, when the procedures areapplied for primary PUCCH group, the terms ‘secondary cell’, ‘secondarycells’, ‘serving cell’, ‘serving cells’ in this clause refer tosecondary cell, secondary cells, serving cell, serving cells belongingto the primary PUCCH group respectively. For example, when theprocedures are applied for secondary PUCCH group, the terms ‘secondarycell’, ‘secondary cells’, ‘serving cell’, ‘serving cells’ in this clauserefer to secondary cell, secondary cells, serving cell, serving cellsbelonging to the secondary PUCCH group respectively.

In an example, if the UE transmits PUSCH without a simultaneous PUCCHfor the serving cell c, then the UE transmit power {circumflex over(P)}_(PUSCH,c)(i) for PUSCH transmission in subframe i for the servingcell c may be given by

${{{{P_{{PUSCH},c}(i)} = {\min\begin{Bmatrix}{{P_{{CMAX},c}(i)},} \\{{10{\log_{10}\left( {M_{{PUSCH},c}(i)} \right)}} + {P_{{O\_ PUSCH},c}(j)} + {{\alpha_{c}(j)} \cdot {PL}_{c}} + {\Delta_{{TF},c}(i)} + {f_{c}(i)}}\end{Bmatrix}}}\text{⁠}}\left\lbrack \text{⁠}{\text{⁠}{dBm}} \right\rbrack}\text{⁠}$

In an example, if the UE transmits PUSCH simultaneous with PUCCH for theserving cell c, then the UE transmit power P_(PUSCH,c)(i) for the PUSCHtransmission in subframe i for the serving cell c may be given by

${P_{{PUSCH},c}(i)} = {\min{\begin{Bmatrix}{{10{\log_{10}\left( {{{\hat{P}}_{{CMAX},c}(i)} - {{\hat{P}}_{PUCCH}(i)}} \right)}},} \\{{10{\log_{10}\left( {M_{{PUSCH},c}(i)} \right)}} + {P_{{O\_ PUSCHc},}(j)} + {{\alpha_{c}(j)} \cdot {PL}_{c}} + {\Delta_{{TF},c}(i)} + {f_{c}(i)}}\end{Bmatrix}\left\lbrack \text{⁠}{{dB}\text{⁠}m}\text{⁠} \right\rbrack}}$

In an example, if the UE is not transmitting PUSCH for the serving cellc, for the accumulation of TPC command received with DCI format 3/3A forPUSCH, the UE may assume that the UE transmit power P_(PUSCH,c)(i) forthe PUSCH transmission in subframe i for the serving cell c is computedby

P _(PUSCH,c)(i)=min{P _(CMAX,c)(i),P _(O_PUSCH,c)(1)+α_(c)(1)·PL _(c) +f_(c)(i)}  [dBm]

In an example, when j=0,P_(O_PUSCH,c)(0)=P_(O_UE_PUSCH,c,2)(0)+P_(O_NOMINAL_PUSCH,c,2)(0), wherej=0 may be used for PUSCH (re)transmissions corresponding to asemi-persistent grant. P_(O_UE_PUSCH,c,2)(0) andP_(O_NOMINAL_PUSCH,c,2)(0) may be the parametersp0-UE-PUSCH-Persistent-SubframeSet2-r12 andp0-NominalPUSCH-Persistent-SubframeSet2-r12 respectively provided byhigher layers, for a serving cell c. In an example, when j=1,P_(O_PUSCH,c)=P_(O_UE_PUSCH,c,2) (1)+P_(O_NOMINAL_PUSCH,c,2)(1), wherej=1 may be used for PUSCH (re)transmissions corresponding to a dynamicscheduled grant. P_(O_UE_PUSCH,c,2)(1) and P_(O_NOMINAL_PUSCH,c,2)(1)may be the parameters p0-UE-PUSCH-SubframeSet2-r12 andp0-NominalPUSCH-SubframeSet2-r12 respectively, provided by higher layersfor serving cell c. In an example, when j=2,P_(O_PUSCH,c)(2)=P_(O_UE_PUSCH,c) (2)+P_(O_NOMINAL_PUSCH,c)(2) whereP_(O_UE_PUSCH,c) (2)=0 andP_(O_NOMINAL_PUSCH,c)(2)=P_(O_PRE)+Δ_(PREAMBLE_Msg3), where theparameter preambleInitialReceivedTargetPower (P_(O_PRE)) andΔ_(PREMBLE_Msg3) may be signalled from higher layers for serving cell c,where j=2 may be used for PUSCH (re)transmissions corresponding to therandom access response grant. For example, when j=3, P_(O_PUSCH,c)(3)=P_(O_UE_PUSCH,c) (3)+P_(O_NOMINAL_PUSCH,c) (3), where j=3 may beused for PUSCH (re)transmissions without a UL grant. P_(O_UE_PUSCH,c)(3) and P_(O_NOMINAL_PUSCH,c) (3) may be the parameters, e.g.,p0-UE-PUSCH-grant-free-SubframeSet2-r12 andp0-NominalPUSCH-grant-free-SubframeSet2-r12, respectively, provided byhigher layers, for a serving cell c.

In an example, P_(O_PUSCH,c) ( ) may be a parameter composed of the sumof a component P_(O_NOMINAL_PUSCH,c) (i) provided from higher layers forj=0 and 1 and a component P_(O_UE_PUSCH,c) (j) provided by higher layersfor j=0 and 1 for serving cell c. For PUSCH (re)transmissionscorresponding to a semi-persistent grant then j=0, for PUSCH(re)transmissions corresponding to a dynamic scheduled grant then j=1and for PUSCH (re)transmissions corresponding to the random accessresponse grant then j=2. P_(O_UE_PUSCH,c) (2)=0 andP_(O_NOMINAL_PUSCH,c) (2)=P_(O_PRE)+Δ_(PREAMBLE_Msg3), where theparameter preambleInitialReceivedTargetPower (P_(O_PRE)) andΔ_(PREAMBLE_Msg3) may be signalled from higher layers for serving cellc.

In an example, if the UE transmits PUSCH without a simultaneous PUCCHfor the serving cell c, then the UE transmit power P_(PUSCH,c)(i) forPUSCH transmission in subframe i for the serving cell c may be given by

${{{P_{{PUSCH},c}(i)} = {\min\begin{Bmatrix}{{P_{{CMAX},c}(i)},} \\{{10{\log_{10}\left( {M_{{PUSCH},c}(i)} \right)}} + {P_{{O\_ PUSCH},c}(j)} + P_{{{GF} - {OFFSET}},c} + {{\alpha_{c}(j)} \cdot {PL}_{c}} + {\Delta_{{TF},c}(i)} + {f_{c}(i)}}\end{Bmatrix}}}\text{⁠}}\lbrack{dBm}\rbrack$

In an example, if the UE transmits PUSCH simultaneous with PUCCH for theserving cell c, then the UE transmit power P_(PUSCH,c)(i) for the PUSCHtransmission in subframe i for the serving cell c may be given by

${P_{{PUSCH},c}(i)} = {\min{\begin{Bmatrix}{{10{\log_{10}\left( {{{\hat{P}}_{{CMAX},c}(i)} - {{\hat{P}}_{PUCCH}(i)}} \right)}},} \\{{10{\log_{10}\left( {M_{{PUSCH},c}(i)} \right)}} + {P_{{O\_ PUSCHc},}(j)} + P_{{{GF} - {OFFSET}},c} + {{\alpha_{c}(j)} \cdot {PL}_{c}} + {\Delta_{{TF},c}(i)} + {f_{c}(i)}}\end{Bmatrix}\left\lbrack \text{⁠}{{dB}\text{⁠}m}\text{⁠} \right\rbrack}}$

In an example, if the UE is not transmitting PUSCH for the serving cellc, for the accumulation of TPC command received with DCI format 3/3A forPUSCH, the UE may assume that the UE transmit power P_(PUSCH,c)(i) forthe PUSCH transmission in subframe i for the serving cell c is computedby

P _(PUSCH,c)(i)=min{P _(CMAX,c)(i),P _(O_PUSCH,c)(1)+P_(GF-OFFSET,c)+α_(c)(1)·PL _(c) +f _(c)(i)}  [dBm]

In an example, P_(GF-OFFSET,c) may be a power offset for PUSCH(re)transmission without a UL grant. P_(GF-OFFSET,c) may be provided byhigher layers, for a serving cell c. For example, P_(GF-OFFSET,c) may bezero for PUSCH (re)transmission with a UL grant, e.g., a semi-persistentgrant and/or dynamic scheduled grant. P_(GF-OFFSET,c) may be non-zeropositive value, e.g., 3 dB, for PUSCH (re)transmission without a ULgrant. In an example, if the UE may be configured with higher layerparameter UplinkPowerControlDedicated-v12x0 for serving cell c and ifsubframe belongs to uplink power control subframe set 2 as indicated bythe higher layer parameter tpc-SubframeSet-r12. In an example, when j=0,P_(O_PUSCH,c)(0)=P_(O_UE_PUSCH,c,2)(0)+P_(O_NOMINAL_PUSCH,c,2)(0), wherej=0 may be used for PUSCH (re)transmissions corresponding to asemi-persistent grant and for PUSCH (re)transmissions with a UL grant.P_(O_UE_PUSCH,c,2) (0) and P_(O_NOMINAL_PUSCH,c,2) (0) may be theparameters p0-UE-PUSCH-Persistent-SubframeSet2-r12 andp0-NominalPUSCH-Persistent-SubframeSet2-r12 respectively provided byhigher layers, for a serving cell c. In an example, when j=1,P_(O_PUSCH,c)(1)=P_(O_UE_PUSCH,c,2)(1)+P_(O_NOMINAL_PUSCH,c,2) (1),where j=1 may be used for PUSCH (re)transmissions corresponding to adynamic scheduled grant. P_(O_UE_PUSCH,c,2)(1) andP_(O_NOMINAL_PUSCH,c,2)(1) may be the parametersp0-UE-PUSCH-SubframeSet2-r12 and p0-NominalPUSCH-SubframeSet2-r12respectively, provided by higher layers for serving cell c. In anexample, when j=2,P_(O_PUSCH,c)(2)=P_(O_UE_PUSCH,c)(2)+P_(O_NOMINAL_PUSCH,c)(2) whereP_(O_UE_PUSCH,c)(2)=0 andP_(O_NOMINAL_PUSCH,c)(2)=P_(O_PRE)+Δ_(PREAMBLE_Msg3), where theparameter preambleInitialReceivedTargetPower (P_(O_PRE)) andΔ_(PREAMBLE_Msg3) may be signalled from higher layers for serving cellc, where j=2 may be used for PUSCH (re)transmissions corresponding tothe random access response grant.

In an example, P_(O_PUSCH,c) (j) may be a parameter composed of the sumof a component P_(O_NOMINAL_PUSCH,c) (j) provided from higher layers forj=0 and 1 and a component P_(O_UE_PUSCH,c) (j) provided by higher layersfor j=0 and 1 for serving cell c. For PUSCH (re)transmissionscorresponding to a semi-persistent grant then j=0, for PUSCH(re)transmissions corresponding to a dynamic scheduled grant then j=1and for PUSCH (re)transmissions corresponding to the random accessresponse grant then j=2. P_(O_UE_PUSCH,c) (2)=0 andP_(O_NOMINAL_PUSCH,c) (2)=P_(O_PRE)+Δ_(PREAMBLE_Msg3), where theparameter preambleInitialReceivedTargetPower (P_(O_PRE)) andΔ_(PREAMBLE_Msg3) may be signalled from higher layers for serving cellc.

In an example, if the UE transmits PUSCH without a simultaneous PUCCHfor the serving cell c, then the UE transmit power P_(PUSCH,c)(i) forPUSCH transmission in subframe i for the serving cell c may be given by

${{{P_{{PUSCH},c}(i)} = {\min\begin{Bmatrix}{{P_{{CMAX},c}(i)},} \\{{10{\log_{10}\left( {M_{{PUSCH},c}(i)} \right)}} + {P_{{O\_ PUSCHc},}(j)} + P_{{{GF} - {rampup}},c} + {{\alpha_{c}(j)} \cdot {PL}_{c}} + {\Delta_{{TF},c}(i)} + {f_{c}(i)}}\end{Bmatrix}}}\text{⁠}}\lbrack{dBm}\rbrack$

In an example, if the UE transmits PUSCH simultaneous with PUCCH for theserving cell c, then the UE transmit power P_(PUSCH,c)(i) for the PUSCHtransmission in subframe i for the serving cell c may be given by

${P_{{PUSCH},c}(i)} = {\min{\begin{Bmatrix}{{10{\log_{10}\left( {{{\hat{P}}_{{CMAX},c}(i)} - {{\hat{P}}_{PUCCH}(i)}} \right)}},} \\{{10{\log_{10}\left( {M_{{PUSCH},c}(i)} \right)}} + {P_{{O\_ PUSCH},c}(j)} + P_{{{GF} - {rampup}},c} + {{\alpha_{c}(j)} \cdot {PL}_{c}} + {\Delta_{{TF},c}(i)} + {f_{c}(i)}}\end{Bmatrix}\left\lbrack \text{⁠}{{dB}\text{⁠}m}\text{⁠} \right\rbrack}}$

In an example, if the UE is not transmitting PUSCH for the serving cellc, for the accumulation of TPC command received with DCI format 3/3A forPUSCH, the UE may assume that the UE transmit power P_(PUSCH,c)(i) forthe PUSCH transmission in subframe i for the serving cell c is computedby

P _(PUSCH,c)(i)=min{P _(CMAX,c)(i),P _(O_PUSCH,c)(1)+P_(GF-rampup,c)+α_(c)(1)·PL _(c) +f _(c)(i)}  [dBm]

In an example, P_(GF-rampup,c) may be a power offset depending on thenumber of GF failures for PUSCH (re)transmission without a UL grant.P_(GF-rampup,c) may be provided by higher layers, for a serving cell c.For example, if PUSCH (re)transmission is with a UL grant, e.g., asemi-persistent grant and/or dynamic scheduled grant, P_(GF-rampup,c)may be zero. For example, if PUSCH (re)transmission is without a ULgrant, P_(GF-rampup,c) may be incremented as P_(GF-rampup,c)(GF_FAILURE_COUNTER−1)*GFpowerRampingStep. For example,GF_FAILURE_COUNTER and GFpowerRampingStep may be provided by higherlayers. For example, GF_FAILURE_COUNTER may start from 1 and beincremented by 1 if a GF failure is detected and reset to 1 when apositive or negative acknowledgement is received by a UE from a gNB; orP_(GF-rampup,c) may be P_(GF-rampup,c)=GFpowerRampingStep if a GFfailure is detected in a previous GF transmission, whereinGFpowerRampingStep may be provided by higher layers. Otherwise,P_(GF-rampup,c) may be zero.

In an example, if the UE may be configured with higher layer parameterUplinkPowerControlDedicated-v12x0 for serving cell c and if subframebelongs to uplink power control subframe set 2 as indicated by thehigher layer parameter tpc-SubframeSet-r12, when j=0,P_(O_PUSCH,c)(0)=P_(O_UE_PUSCHc,2)(0)+P_(O_NOMINAL_PUSCH,c,2)(0), wherej=0 may be used for PUSCH (re)transmissions corresponding to asemi-persistent grant and for PUSCH (re)transmissions with a UL grant.P_(O_UE_PUSCH,c,2)(0) and P_(O_NOMINAL_PUSCH,c,2)(0) may be theparameters p0-UE-PUSCH-Persistent-SubframeSet2-r12 andp0-NominalPUSCH-Persistent-SubframeSet2-r12 respectively provided byhigher layers, for a serving cell c.

In an example, when j=1, P_(O_PUSCH,c)(1)=P_(O_UE_PUSCH,c,2)(1)+P_(O_NOMINAL_PUSCH,c,2) (1), where j=1 may beused for PUSCH (re)transmissions corresponding to a dynamic scheduledgrant. P_(O_UE_PUSCH,c,2)(1) and P_(O_NOMINAL_PUSCH,c,2)(1) may be theparameters p0-UE-PUSCH-SubframeSet2-r12 andp0-NominalPUSCH-SubframeSet2-r12 respectively, provided by higher layersfor serving cell c.

For example, whenj=2,P_(O_PUSCH,c)(2)=P_(O_UE_PUSCH,c)(2)+P_(O_NOMINAL_PUSCH,c)(2) whereP_(O_UE_PUSCH,c)(2)=0 and P_(O_NOMINAL_PUSCH,c)(2)=P_(O_PRE)+Δ_(PREAMBLE_Msg3), where the parameterpreambleInitialReceivedTargetPower (P_(O_PRE)) and Δ_(PREAMBLE_Msg3) maybe signalled from higher layers for serving cell c, where j=2 may beused for PUSCH (re)transmissions corresponding to the random accessresponse grant.

In an example, P_(O_PUSCH,c) U) may be a parameter composed of the sumof a component P_(O_NOMINAL_PUSCH,c) (i) provided from higher layers forj=0 and 1 and a component P_(O_UE_PUSCH,c) (i) provided by higher layersfor j=0 and 1 for serving cell c. For PUSCH (re)transmissionscorresponding to a semi-persistent grant then j=0, for PUSCH(re)transmissions corresponding to a dynamic scheduled grant then j=1and for PUSCH (re)transmissions corresponding to the random accessresponse grant then j=2. P_(O_UE_PUSCH,c) (2)=0 andP_(O_NOMINAL_PUSCH,c) (2)=P_(O_PRE)+Δ_(PREAMBLE_Msg3), where theparameter preambleInitialReceivedTargetPower (P_(O_PRE)) andΔ_(PREAMBLE_Msg3) may be signalled from higher layers for serving cellc. P_(PUSCH,c)(i) for PUSCH transmission in subframe i for the servingcell c.

In an example, P_(CMAX,c)(i) may be the configured UE transmit power insubframe i for serving cell c and {circumflex over (P)}_(CMAX,c) (i) maybe the linear value of P_(CMAX,c) (i) In an example, if the UE transmitsPUCCH without PUSCH in subframe i for the serving cell c, for theaccumulation of TPC command received with DCI format 3/3A for PUSCH, theUE may assume P_(CMAX,c)(i). In an example, if the UE does not transmitPUCCH and PUSCH in subframe i for the serving cell c, for theaccumulation of TPC command received with DCI format 3/3A for PUSCH, theUE may compute P_(CMAX,c)(i) assuming MPR=0 dB, A-MPR=0 dB, P-MPR=0 dBand ΔT_(C)=0 dB, where MPR, A-MPR, P-MPR and ΔT_(C) may be pre-definedin LTE technology. In an example, {circumflex over (P)}_(PUCCH)(i) maybe the linear value of P_(PUCCH) (i). In an example, M_(PUSCH,c) (i) maybe the bandwidth of the PUSCH resource assignment expressed in number ofresource blocks valid for subframe i and serving cell c.

In an example, if the UE may be configured with higher layer parameterUplinkPowerControlDedicated-v12x0 for serving cell c and if subframe ibelongs to uplink power control subframe set 2 as indicated by thehigher layer parameter tpc-SubframeSet-r12, e.g., for j=0 or 1,α_(c)(j)=α_(c,2) ∈(0, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1). α_(c,2) may bethe parameter alpha-SubframeSet2-r12 provided by higher layers for aserving cell c. For example, for j=2, α_(c)(j)=1. For j=0 or 1,α_(c)∈{0, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1} may be a 3-bit parameterprovided by higher layers for serving cell c. For j=2, α_(c)(j)=1.

PL_(c) may be the downlink path loss estimate calculated in the UE forserving cell c in dB and PL_(c)=referenceSignalPower−higher layerfiltered RSRP, where referenceSignalPower may be provided by higherlayers and RSRP may be defined for the reference serving cell and thehigher layer filter configuration may be defined for the referenceserving cell.

In an example, if serving cell c belongs to a TAG containing the primarycell then, for the uplink of the primary cell, the primary cell may beused as the reference serving cell for determining referenceSignalPowerand higher layer filtered RSRP. For the uplink of the secondary cell,the serving cell configured by the higher layer parameterpathlossReferenceLinking may be used as the reference serving cell fordetermining referenceSignalPower and higher layer filtered RSRP.

In an example, if serving cell c belongs to a TAG containing the PSCellthen, for the uplink of the PSCell, the PSCell may be used as thereference serving cell for determining referenceSignalPower and higherlayer filtered RSRP; for the uplink of the secondary cell other thanPSCell, the serving cell configured by the higher layer parameterpathlossReferenceLinking may be used as the reference serving cell fordetermining referenceSignalPower and higher layer filtered RSRP.

In an example, if serving cell c belongs to a TAG not containing theprimary cell or PSCell then serving cell c may be used as the referenceserving cell for determining referenceSignalPower and higher layerfiltered RSRP.

Δ_(TF,c)(i)=10 log₁₀ (2^(BPRE·K) ^(s) −1)·β_(offset) ^(PUSCH)) forK_(S)=1.25 and 0 for K_(S)=0 where K_(S) may be given by the parameterdeltaMCS-Enabled provided by higher layers for a serving cell c. BPREand β_(offset) ^(PUSCH), for a serving cell c, may be computed as below.K_(S)=0 for transmission mode 2. For example, BPRE=O_(CQI)/N_(RE) forcontrol data sent via PUSCH without UL-SCH data and

$\sum\limits_{r = 0}^{C - 1}{K_{r}/N_{RE}}$

for other cases. In an example, c may be the number of code blocks,K_(r) may be the size for code block r, O_(CQI) may be the number ofCQI/PMI bits including CRC bits and N_(RE) may be the number of resourceelements determined as N_(RE)=M_(sc) ^(PUSCH-initial)·N_(symb)^(PUSCH-initial) where C, K_(r), M_(sc) ^(PUSCH-initial) and N_(symb)^(PUSCH-initial) may be pre-defined in LTE technology. In an example,the UE may set β_(offset) ^(PUSCH)=β_(offset) ^(CQI) for control datasent via PUSCH without UL-SCH data and 1 for other cases.

δ_(PUSCH,c) may be a correction value, also referred to as a TPC commandand may be included in PDCCH/EPDCCH with DCI format 0/0A/0B/4/4A/4B orin MPDCCH with DCI format 6-0A for serving cell c or jointly coded withother TPC commands in PDCCH/MPDCCH with DCI format 3/3A whose CRC paritybits may be scrambled with TPC-PUSCH-RNTI. In an example, if the UE maybe configured with higher layer parameterUplinkPowerControlDedicated-v12x0 for serving cell c and if subframe ibelongs to uplink power control subframe set 2 as indicated by thehigher layer parameter tpc-SubframeSet-r12, the current PUSCH powercontrol adjustment state for serving cell c may be given by f_(c,2)(i),and the UE may use f_(c,2) (i) instead of f_(c)(i) to determineP_(PUSCH,c)(i). Otherwise, the current PUSCH power control adjustmentstate for serving cell c may be given by f_(c)(i).

For example, f_(c,2)(i) and f_(c)(i) may be defined by f_(c)(i)=f_(c)(i−1)+δ_(PUSCH,c) (i−K_(PUSCH)) and f_(c,2)(i)=f_(c,2)(i−1)+δ_(PUSCH,c)(i−K_(PUSCH)) if accumulation may be enabled based onthe parameter Accumulation-enabled provided by higher layers or if theTPC command δ_(PUSCH,c) may be included in a PDCCH/EPDCCH with DCIformat 0 or in a MPDCCH with DCI format 6-0A for serving cell c wherethe CRC may be scrambled by the Temporary C-RNTI. For example,δ_(PUSCH,c)(i−K_(PUSCH)) was signalled on PDCCH/EPDCCH with DCI format0/0A/0B/4/4A/4B or MPDCCH with DCI format 6-0A or PDCCH/MPDCCH with DCIformat 3/3A on subframe i−K_(PUSCH), and where f_(c)(0) may be the firstvalue after reset of accumulation. For a BL/CE UE configured withCEModeA, subframe i−K_(PUSCH) may be the last subframe in which theMPDCCH with DCI format 6-0A or MPDCCH with DCI format 3/3A may betransmitted.

For example, the value of K_(PUSCH) may be determined as one offollowings: K_(PUSCH)=4 for FDD or FDD-TDD and serving cell framestructure type 1; For TDD, if the UE may be configured with more thanone serving cell and the TDD UL/DL configuration of at least twoconfigured serving cells may be not the same, or if the UE may beconfigured with the parameter EIMTA-MainConfigServCell-r12 for at leastone serving cell, or for FDD-TDD and serving cell frame structure type2, the “TDD UL/DL configuration” refers to the UL-reference UL/DLconfiguration for serving cell c; For TDD UL/DL configurations 1-6,K_(PUSCH) may be given in FIG. 28A; if the PUSCH transmission insubframe 2 or 7 may be scheduled with a PDCCH/EPDCCH of DCI format 0/4or a MPDCCH of DCI format 6-0A in which the LSB of the UL index may beset to 1, K_(PUSCH)=7 for TDD UL/DL configuration 0; and For other PUSCHtransmissions, K_(PUSCH) may be given in FIG. 28A.

For example, for a serving cell with frame structure type 3, e.g., foran uplink DCI format 0A/0B/4A/4B with PUSCH trigger A set to 0,K_(PUSCH) may be equal to k+l, where k and l may be pre-defined in LTEtechnology. For example, for a serving cell with frame structure type 3,e.g., for an uplink DCI format 0A/0B/4A/4B with PUSCH trigger A set to 1and upon the detection of PDCCH with DCI CRC scrambled by CC-RNTI andwith ‘PUSCH trigger B’ field set to ‘1’, K_(PUSCH) may be equal top+k+l, where p, k and l may be pre-defined in LTE technology. In anexample, if a UE detected multiple TPC commands in subframe i−K_(PUSCH),the UE may use the TPC command in the PDCCH/EPDCCH with DCI format0A/0B/4A/4B which schedules PUSCH transmission in subframe i.

In an example, for serving cell c and a non-BL/CE UE, the UE attempts todecode a PDCCH/EPDCCH of DCI format 0/0A/0B/4/4A/4B with the UE's C-RNTIor DCI format 0 for SPS C-RNTI and a PDCCH of DCI format 3/3A with thisUE's TPC-PUSCH-RNTI in every subframe except when in DRX or whereserving cell c may be deactivated. For serving cell c and a BL/CE UEconfigured with CEModeA, the UE attempts to decode a MPDCCH of DCIformat 6-0A with the UE's C-RNTI or SPS C-RNTI and a MPDCCH of DCIformat 3/3A with this UE's TPC-PUSCH-RNTI in every BL/CE downlinksubframe except when in DRX

For a non-BL/CE UE, if DCI format 0/0A/0B/4/4A/4B for serving cell c andDCI format 3/3A may be both detected in the same subframe, then the UEmay use the δ_(PUSCH,c) provided in DCI format 0/0A/0B/4/4A/4B. For aBL/CE UE configured with CEModeA, if DCI format 6-0A for serving cell cand DCI format 3/3A may be both detected in the same subframe, then theUE may use the δ_(PUSCH,c) provided in DCI format 6-0A. For example, thewireless device may determine δ_(PUSCH,c)=0 dB for a subframe where noTPC command may be decoded for serving cell c or where DRX occurs or imay be not an uplink subframe in TDD or FDD-TDD and serving cell c framestructure type 2. For example, the wireless device may determineδ_(PUSCH,c)=0 dB if the subframe i may be not the first subframescheduled by a PDCCH/EPDCCH of DCI format 0B/4B. For example, theδ_(PUSCH,c) dB accumulated values signalled on PDCCH/EPDCCH with DCIformat 0/0A/0B/4/4A/4B or MPDCCH with DCI format 6-0A may be given inFIG. 28B. In an example, if the PDCCH/EPDCCH with DCI format 0 or MPDCCHwith DCI format 6-0A may be validated as a SPS activation or releasePDCCH/EPDCCH/MPDCCH, then δ_(PUSCH,c) may be 0 dB. For example, theδ_(PUSCH) dB accumulated values signalled on PDCCH/MPDCCH with DCIformat 3/3A may be one of SET1 given in FIG. 28B or SET2 given in FIG.28C as determined by the parameter TPC-Index provided by higher layers.

In an example, if UE has reached P_(CMAX,c)(i) for serving cell c,positive TPC commands for serving cell c may not be accumulated. In anexample, if UE has reached minimum power, negative TPC commands may notbe accumulated.

In an example, if the UE may be not configured with higher layerparameter UplinkPowerControlDedicated-v12x0 for serving cell c, the UEmay reset accumulation for serving cell c, when P_(O_UE_PUSCH,c) valuemay be changed by higher layers for example when the UE receives randomaccess response message for serving cell c. In an example, if the UE maybe configured with higher layer parameterUplinkPowerControlDedicated-v12x0 for serving cell c, the UE may resetaccumulation corresponding to f_(c) (*) for serving cell c, for example,when P_(O_UE_PUSCH,c) value may be changed by higher layers and/or, forexample, when the UE receives random access response message for servingcell c. In an example, if the UE may be configured with higher layerparameter UplinkPowerControlDedicated-v12x0 for serving cell c, the UEmay reset accumulation corresponding to f_(c,2)(*) for serving cell c,for example, when P_(O_UE_PUSCHc,2) value may be changed by higherlayers.

In an example, if the UE may be configured with higher layer parameterUplinkPowerControlDedicated-v12x0 for serving cell c and/or if subframei belongs to uplink power control subframe set 2 as indicated by thehigher layer parameter tpc-SubframeSet-r12, the UE may set tof_(c)(i)=f_(c)(i−1). In an example, if the UE may be configured withhigher layer parameter UplinkPowerControlDedicated-v12x0 for servingcell c and/or if subframe i does not belong to uplink power controlsubframe set 2 as indicated by the higher layer parametertpc-SubframeSet-r12 the UE may set to f_(c,2)(i)=f_(c,2)(i−1)

For example, f_(c,2)(i) and f_(c)(i) may be defined by:f_(c)(i)=δ_(PUSCH,c)(i−K_(PUSCH)) and f_(c,2)(i)=δ_(PUSCH,c)(i−K_(PUSCH)) if accumulation may be not enabled for serving cell cbased on the parameter Accumulation-enabled provided by higher layers.For example, δ_(PUSCH,c) (i−K_(PUSCH)) was signalled on PDCCH/EPDCCHwith DCI format 0/0A/0B/4/4A/4B or MPDCCH with DCI format 6-0A forserving cell c on subframe i−K_(PUSCH). For a BL/CE UE configured withCEModeA, subframe i−K_(PUSCH) may be the last subframe in which theMPDCCH with DCI format 6-0A or MPDCCH with DCI format 3/3A may betransmitted.

The value of K_(PUSCH) may be determined one of following: For FDD orFDD-TDD and serving cell frame structure type 1, K_(PUSCH)=4; For TDD,if the UE may be configured with more than one serving cell and the TDDUL/DL configuration of at least two configured serving cells may be notthe same, or if the UE may be configured with the parameterEIMTA-MainConfigServCell-r12 for at least one serving cell, or FDD-TDDand serving cell frame structure type 2, the “TDD UL/DL configuration”refers to the UL-reference UL/DL configuration for serving cell c; ForTDD UL/DL configurations 1-6, K_(PUSCH) may be given in FIG. 28A; ForTDD UL/DL configuration 0; if the PUSCH transmission in subframe 2 or 7may be scheduled with a PDCCH/EPDCCH of DCI format 0/4 or a MPDCCH withDCI format 6-0A in which the LSB of the UL index may be set to 1,K_(PUSCH)=7; For other PUSCH transmissions, K_(PUSCH) may be given inFIG. 28A.

In an example, the value of K_(PUSCH) may be determined one offollowing: For a serving cell with frame structure type 3; For an uplinkDCI format 0A/4A with PUSCH trigger A set to 0, K_(PUSCH) may be equalto k+l, where k and l may be pre-defined in the power control operation;For an uplink DCI format 0B/4B with PUSCH trigger A set to 0, K_(PUSCH)may be equal to k+l+i′ with i′=mod(n_(HARQ_ID)^(i)−n_(HARQ_ID),N_(HARQ)), where n^(i) _(HARQ_ID) may be HARQ processnumber in subframe i, and k, l, n_(HARQ_ID) and N_(HARQ) may bepre-defined in the power control operation; For an uplink DCI format0A/4A with PUSCH trigger A set to 1 and upon the detection of PDCCH withDCI CRC scrambled by CC-RNTI and with ‘PUSCH trigger B’ field set to‘1’, K_(PUSCH) may be equal to p+k+l, where p, k and l may bepre-defined in the power control operation; for an uplink DCI format0B/4B with PUSCH trigger A set to 1 and upon the detection of PDCCH withDCI CRC scrambled by CC-RNTI and with ‘PUSCH trigger B’ field set to‘1’, K_(PUSCH) may be equal to p+k+l+i′ with i′=mod(n_(HARQ_ID)^(i)−n_(HARQ_ID),N_(HARQ)), where n^(i) _(HARQ_ID) may be HARQ processnumber in subframe i, and p, k, l, n_(HARQ_ID) and N_(HARQ) may bepre-defined in power control operation. In an example, if a UE detectedmultiple TPC commands in subframe i−K_(PUSCH), the UE may use the TPCcommand in the PDCCH/EPDCCH with DCI format 0A/0B/4A/4B which schedulesPUSCH transmission in subframe i.

The δ_(PUSCH),c dB absolute values signalled on PDCCH/EPDCCH with DCIformat 0/0A/0B/4/4A/4B or a MPDCCH with DCI format 6-0A may be given inFIG. 28B. In an example, if the PDCCH/EPDCCH with DCI format 0 or aMPDCCH with DCI format 6-0A may be validated as a SPS activation orrelease PDCCH/EPDCCH/MPDCCH, then δ_(PUSCH,c) may be 0 dB.

In an example, e.g., for a non-BL/CE UE, f_(c)(i)=f_(c)(i−1) and f_(c,2)(i)=f_(c,2) (i−1) for a subframe where no PDCCH/EPDCCH with DCI format0/0A/0B/4/4A/4B may be decoded for serving cell c or where DRX occurs ori may be not an uplink subframe in TDD or FDD-TDD and serving cell cframe structure type 2. In an example, e.g., for a BL/CE UE configuredwith CEModeA, f_(c)(i)=f_(c)(i−1) and f_(c,2) (i)=f_(c,2) (i−1) for asubframe where no MPDCCH with DCI format 6-0A may be decoded for servingcell c or where DRX occurs or i may be not an uplink subframe in TDD.

In an example, the UE may set f_(c)(i)=f_(c)(i−1) if the UE may beconfigured with higher layer parameter UplinkPowerControlDedicated-v12x0for serving cell c and if subframe belongs to uplink power controlsubframe set 2 as indicated by the higher layer parametertpc-SubframeSet-r12. In an example, the UE may setf_(c,2)(i)=f_(c,2)(i−1) if the UE may be configured with higher layerparameter UplinkPowerControlDedicated-v12x0 for serving cell c and ifsubframe does not belong to uplink power control subframe set 2 asindicated by the higher layer parameter tpc-SubframeSet-r12

In an example, for both types of f_(c) (*) (accumulation or currentabsolute) the first value may be set f_(c) (0)=0, for example, ifP_(O_UE_PUSCH,c) value is changed by higher layers and serving cell c isthe primary cell or, if P_(O_UE_PUSCH,c) value is received by higherlayers and serving cell c is a Secondary cell. For example, if the UEreceives the random access response message for a serving cell c, forf_(c) (*) (accumulation or current absolute) the first value may be setf_(c)(0)=Δ_(rampup,c)+δ_(msg2,c). In an example, δ_(msg2,c) may be theTPC command indicated in the random access response corresponding to therandom access preamble transmitted in the serving cell c, and

$\begin{matrix}{{\Delta P_{{rampup},c}} = {\min\left\lbrack {\left\{ {\max\left( {0,{P_{{CMAX},c} - \begin{pmatrix}{10{\log}_{10}\left( {M_{{PUSCH},c}(0)} \right)} \\{{+ {P_{{O\_ PUSCH},c}(2)}} + \delta_{{msg}2}} \\{{{+ {\alpha_{c}(2)}} \cdot {PL}} + {\Delta_{{TF},c}(0)}}\end{pmatrix}}} \right)} \right\},} \right.}} & \left. {\Delta P_{{rampuprequested},c}} \right\rbrack\end{matrix}$

and ΔP_(rampuprequested,c) may be provided by higher layers andcorrespond to the total power ramp-up requested by higher layers fromthe first to the last preamble in the serving cell c, M_(PUSCH,c)(0) maybe the bandwidth of the PUSCH resource assignment expressed in number ofresource blocks valid for the subframe of first PUSCH transmission inthe serving cell c, and ΔTF,c(0) is the power adjustment of first PUSCHtransmission in the serving cell c. In an example, for both types of(accumulation or current absolute) the first value may be setf_(c,2)(0)=0, for example, if P_(O_UE_PUSCHc,2) value is received byhigher layers for a serving cell c.

According to various embodiments, a device such as, for example, awireless device, off-network wireless device, a base station, and/or thelike, may comprise one or more processors and memory. The memory maystore instructions that, when executed by the one or more processors,cause the device to perform a series of actions. Embodiments of exampleactions are illustrated in the accompanying figures and specification.Features from various embodiments may be combined to create yet furtherembodiments.

FIG. 29 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 2910, a wireless device may receive a radioresource control message. The radio resource control message maycomprise one or more first configuration parameters of a configuredperiodic grant of a first type. The one or more first configurationparameters may indicate a timing offset and a symbol number thatidentify a resource of an uplink grant of the configured periodic grant.The one or more first configuration parameters may indicate a firstperiodicity of the configured periodic grant. The first periodicity mayindicate a time interval between two subsequent resources of theconfigured periodic grant. The one or more first configurationparameters may indicate one or more demodulation reference signalparameters of the configured periodic grant. At 2920, the configuredperiodic grant may be activated in response to the radio resourcecontrol message. At 2930, one or more symbols of the resource of theuplink grant of the configured periodic grant may be determined based onthe timing offset, the symbol number, and the first periodicity. At2940, one or more transport blocks transmitted via the resourceemploying the one or more demodulation reference signal parameters.

According to an embodiment, the configured periodic grant may start froma first symbol based on: the timing offset; and the symbol number. Theconfigured periodic grant may reoccur with the first periodicity.According to an embodiment, the one or more first configurationparameters may comprise a value indicating a number of repetitions ofthe one or more transport blocks. According to an embodiment, the radioresource control message may comprise an identifier of the configuredperiodic grant. According to an embodiment, the wireless device mayreceive from a base station, a second message indicating a release ofthe one or more first configuration parameters. According to anembodiment, the wireless device may release the one or more firstconfiguration parameters in response to receiving the second message.According to an embodiment, the second message comprises the identifierof the configured periodic grant. According to an embodiment, furthercomprising determining a first transmit power for a transmission of theone or more transport blocks at least based on a first power offsetvalue of the configured periodic grant of the first type.

According to an embodiment, a second radio resource control message maybe received. The second radio resource control message may comprise oneor more second configuration parameters of a configured periodic grantof a second type. The one or more second configuration parameters mayindicate a second periodicity of the configured periodic grant of thesecond type. According to an embodiment, a downlink control informationin a second symbol may be received. According to an embodiment, theconfigured periodic grant of the second type may be activated inresponse to receiving the downlink control information. The configuredperiodic grant of the second type: may start in a third symbol based onthe second symbol; and may reoccur with the second periodicity.According to an embodiment, a second symbol number may be determinedbased on the second symbol and the second periodicity. The second symbolnumber may indicate a second resource of a second uplink grant of theconfigured periodic grant of the second type. According to anembodiment, one or more second transport blocks may be transmitted viathe second resource of the configured periodic grant of the second type.

According to an embodiment, the first radio resource control message andthe second radio resource control message may be the same. According toan embodiment, a second transmit power of transmission of the one ormore second transport blocks may be determined at least based on asecond power offset value of the configured periodic grant of the secondtype.

FIG. 30 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 3010, a wireless device may receive a radioresource control message. The radio resource control message maycomprise one or more first configuration parameters of a configuredperiodic grant of a first type. The one or more first configurationparameters may indicate a timing offset and a symbol number thatidentify a resource of an uplink grant of the configured periodic grant.The one or more first configuration parameters may indicate a firstperiodicity of the configured periodic grant. The first periodicity mayindicate a time interval between two subsequent resources of theconfigured periodic grant. The one or more first configurationparameters may indicate at least one first power offset value of theconfigured periodic grant. At 3020, the configured periodic grant may beactivated in response to the radio resource control message. At 3030,first transmission power for a transmission of at least one transportblock of the configured periodic grant may be determined based on the atleast one first power offset value. At 3040, one or more transportblocks may be transmitted with the first transmission power. Accordingto an embodiment, the first transmission power may be determining basedon: a ramp-up power value; and a pathloss value estimated based on oneor more reference signals. According to an embodiment, the ramp-up powervalue may be determined based on a counter indicating a number of timesthat the wireless device does not received, from the base station, anacknowledgement in response to transmitting the at least one transportblock.

FIG. 31 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 3110, a wireless device may receive, from abase station, a first radio resource control message. The first radioresource control message may indicate at least one value of adiscontinuous reception (DRX) uplink retransmission timer. The firstradio resource control message may indicate that at least one value isassociated with a configured periodic grant of a first type. At 3120, atleast one transport block may be transmitted via a radio resource. At3130, the DRX uplink retransmission timer may be started based on the atleast one value in response to the radio resource being associated withthe configured periodic grant. According to an embodiment, at least onesecond transport block may be transmitted via a second radio resource.According to an embodiment, the DRX uplink retransmission timer may bestopped in response to the second radio resource being associated withthe configured periodic grant. According to an embodiment, the at leastone second transport block may be the at least one transport block.According to an embodiment, an active time duration of a DRX may bedetermined based on the DRX uplink retransmission timer.

FIG. 32 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 3210, a wireless device may receive, from abase station, one or more first radio resource control messages. The oneor more first radio resource control messages may comprise at least oneparameter indicating whether a configured periodic grant of a first typecan be used for transmission of data of a first logical channel. The oneor more first radio resource control messages may comprise a timingoffset and a symbol number that identify a resource of an uplink grantof the configured periodic grant of the first type. The one or morefirst radio resource control messages may comprise a first periodicityof the configured periodic grant of the first type. The firstperiodicity may indicate a time interval between two subsequentresources of the configured periodic grant of the first type. At 3220,the configured periodic grant of the first type may be activated inresponse to receiving the first radio resource control message. At 3230,the data of the first logical channel may be multiplexed onto one ormore transport blocks for transmission via the resource in response tothe at least one parameter indicating that the configured periodic grantof the first type can be used by the first logical channel. At 3240, theone or more transport blocks may be transmitted via the resource of theconfigured periodic grant of the first type.

According to an embodiment, the configured periodic grant of the firsttype may start from a first symbol based on: the timing offset; and thesymbol number. The configured periodic grant of the first type mayreoccur with the first periodicity. According to an embodiment, based ona first size of the data, a determination may be made to transmit theone or more transport blocks via the resource of the configured periodicgrant of the first type. According to an embodiment, the one or moretransport blocks may be transmitted in response to the first size beinglarger than a first value. A second size of the resource of theconfigured periodic grant of the first type may determine the firstvalue. According to an embodiment, one or more symbols of the resourceof the uplink grant of the configured periodic grant of the first typemay be determined based on the timing offset, the symbol number, and thefirst periodicity.

According to an embodiment, a second radio resource control message maybe received. The second radio resource control message may comprise oneor more second configuration parameters of a configured periodic grantof a second type. The one or more second configuration parameters maycomprise a second periodicity of the configured periodic grant of thesecond type. According to an embodiment, a downlink control informationin a second symbol may be received. According to an embodiment, inresponse to receiving the downlink control information, the configuredperiodic grant of the second type to start in a third symbol based onthe second symbol may be activated. The configured periodic grant of thesecond type may reoccur with the second periodicity. According to anembodiment, one or more second transport blocks may be transmitted via asecond resource of the configured periodic grant of the second type.

According to an embodiment, one or more second symbols of the secondresource may be determined based on the second symbol and the secondperiodicity. According to an embodiment, the first radio resourcecontrol message and the second radio resource control message may be thesame. According to an embodiment, the wireless device may receive, fromthe base station, a third radio resource control message indicating arelease of the configured periodic grant of the first type. Theconfigured periodic grant of the first type may be released in responseto receiving the third message. According to an embodiment, the wirelessdevice may transmit, via the resource of the configured periodic grantof the first type, the one or more transport blocks based on a firstsize of the data. According to an embodiment, the wireless device maytransmit, via the resource of the configured periodic grant of the firsttype, the one or more transport blocks in response to the first sizebeing larger than a first value. A second size of the resource of theconfigured periodic grant of the first type may determine the firstvalue. According to an embodiment, the wireless device may receive, fromthe base station, a third radio resource control message indicating arelease of the configured periodic grant of the second type. Accordingto an embodiment, the wireless device may release the configuredperiodic grant of the second type in response to receiving the secondmessage.

FIG. 33 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 3310, a base station may transmit to awireless device, one or more first radio resource control messages. Theone or more first radio resource control messages may comprise at leastone parameter indicating whether a configured periodic grant of a firsttype can be used for transmission of data of a first logical channel.The one or more first radio resource control messages may comprise atiming offset and a symbol number that identify a resource of an uplinkgrant of the configured periodic grant of the first type. The one ormore first radio resource control messages may comprise a firstperiodicity of the configured periodic grant of the first type. Thefirst periodicity may indicate a time interval between two subsequentresources of the configured periodic grant of the first type. At 3320,the configured periodic grant of the first type may be activated inresponse to receiving the first radio resource control message. At 3330,one or more transport blocks may be received via the resource of theconfigured periodic grant of the first type. At 3340, the one or moretransport blocks may be demultiplexing into the data of the firstlogical channel in response to the at least one parameter indicatingthat the configured periodic grant of the first type can be used by thefirst logical channel.

According to an embodiment, the configured periodic grant of the firsttype may start from a first symbol based on: the timing offset; and thesymbol number. According to an embodiment, the configured periodic grantof the first type may reoccur with the first periodicity.

FIG. 34 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 3410, a wireless device may receive one ormore radio resource control messages from a base station. The one ormore radio resource control messages may comprise at least one parameterindicating that a configured periodic grant of a first type can be usedfor transmission of data of a first logical channel. The one or moreradio resource control messages may comprise a timing offset and asymbol number that identify a resource of an uplink grant of theconfigured periodic grant of the first type. The one or more radioresource control messages may comprise a first periodicity of theconfigured periodic grant of the first type. The first periodicity mayindicate a time interval between two subsequent resources of theconfigured periodic grant of the first type. At 3420, the configuredperiodic grant of the first type may be activated in response toreceiving the one or more radio resource control messages. At 3430, abuffer status report (BSR) may be multiplexed onto at least one packetin response to a size of the data of the first logical channel beinglarger than a first threshold. The BSR may indicate the size of thedata. At 3440, the at least one packet may be transmitted via theresource.

According to an embodiment, the one or more radio resource controlmessages may comprise the first threshold. According to an embodiment,the wireless device may determine the first threshold based on a secondsize of the resource. According to an embodiment, the BSR may be aregular BSR. According to an embodiment, the configured periodic grantof the first type may start from a first symbol based on: the timingoffset and the symbol number. The configured periodic grant of the firsttype may reoccur with the first periodicity. According to an embodiment,an uplink scheduling request may be triggered in response to receivingno uplink grant corresponding to the BSR. According to an embodiment,the wireless device may receive one or more uplink grants from the basestation in response to transmitting the BSR.

FIG. 35 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 3510, a wireless device may receive one ormore radio resource control messages from a base station. The one ormore radio resource control messages may comprise at least one firstparameter of a configured periodic grant of a first type. The one ormore radio resource control messages may comprise a second parameter ofa first logical channel. At 3520, a BSR may be multiplexed onto at leastone packet in response to a size of the data of the first logicalchannel being larger than a first threshold. The BSR may indicate thesize of the data. At 3530, the at least one packet may be transmittedvia a resource of the configured periodic grant of the first type.

According to an embodiment, the at least one first parameter mayindicate a timing offset and a symbol number that identify a resource ofan uplink grant of the configured periodic grant of the first type. Theat least one first parameter may identify a first periodicity of theconfigured periodic grant of the first type. The first periodicity mayindicate a time interval between two subsequent resources of theconfigured periodic grant of the first type. According to an embodiment,in response to receiving the one or more radio resource controlmessages, the configured periodic grant of the first type may beactivated. According to an embodiment, the configured periodic grant ofthe first type may start from a first symbol based on: the timingoffset; and the symbol number. The configured periodic grant of thefirst type may reoccur with the first periodicity. According to anembodiment, the second parameter may indicate that the configuredperiodic grant of the first type can be used for transmission of data ofa first logical channel. According to an embodiment, the one or moreradio resource control messages may comprise the first threshold.According to an embodiment, the wireless device may determine the firstthreshold based on a second size of the resource. According to anembodiment, the BSR maybe a regular BSR. According to an embodiment, anuplink scheduling request may be triggered in response to receiving nouplink grant corresponding to the BSR. According to an embodiment, thewireless device may receive from the base station, one or more uplinkgrants in response to transmitting the BSR.

FIG. 36 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 3610, a base station may transmit one or moreradio resource control messages to a wireless device. The one or moreradio resource control messages may comprise at least one parameterindicating that a configured periodic grant of a first type can be usedfor transmission of data of a first logical channel. The one or moreradio resource control messages may comprise a timing offset and asymbol number that identify a resource of an uplink grant of theconfigured periodic grant of the first type. The one or more radioresource control messages may comprise a first periodicity of theconfigured periodic grant of the first type, the first periodicityindicating a time interval between two subsequent resources of theconfigured periodic grant of the first type. At 3620, the configuredperiodic grant of the first type may be activated in response toreceiving the one or more radio resource control message. At 3630, atleast one packet comprising a multiplexed buffer status report (BSR) maybe received, via the resource, in response to a size of the data of thefirst logical channel being larger than a first threshold. The BSR mayindicate the size of the data. According to an embodiment, the one ormore radio resource control messages may comprise the first threshold.According to an embodiment, the base station may determine the firstthreshold based on a second size of the resource.

FIG. 37 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 3710, a wireless device may receive at leastone first message from a base station. The at least one first messagemay comprise at least one configuration parameter indicating a timingoffset and a symbol number that identify a resource of an uplink grantof a configured periodic grant of a first type. The at least one firstmessage may comprise at least one configuration parameter indicating afirst periodicity of the configured periodic grant of the first type.The first periodicity indicating a time interval between two subsequentresources of the configured periodic grant of the first type. At 3720,one or more transport blocks may be transmitted via the resource of theconfigured periodic grant of the first type. At 3730, a second messageindicating a request for transmission information associated with theconfigured periodic grant of the first type may be received. At 3740, athird message may be transmitted in response to the second message. Thethird message may comprise one or more parameters indicating at leastone of: a first value based on a number of transmissions via theresource associated with the configured periodic grant of the firsttype; and a second value based on a number of times that the wirelessdevice received no corresponding acknowledgement from the base stationin response to the transmissions.

According to an embodiment, the at least one configuration parameter mayfurther indicate a duration determining the first value and the secondvalue. According to an embodiment, the configured periodic grant of thefirst type may be activated to start from a first symbol based on: thetiming offset; and the symbol number. According to an embodiment, theconfigured periodic grant of the first type may reoccur with the firstperiodicity. According to an embodiment, one or more symbols of theresource of the uplink grant of the configured periodic grant of thefirst type may be determined based on the timing offset, the symbolnumber, and the first periodicity. According to an embodiment, the oneor more parameters may indicate at least one of following: a third valuebased on a number of times that the wireless device receives a positiveor negative acknowledgement from the base station in response to thetransmissions via the resource of the configured periodic grant of thefirst type; and a fourth value based on a number of collisions detectedby the wireless device when the wireless device receives noacknowledgement from the base station in response to the transmissionsvia the configured periodic grant of the first type.

According to an embodiment, the third message may comprise an indicatorthat indicates whether the wireless device detects one or morecollisions when the wireless device receives no acknowledgement from thebase station in response to the transmissions via the configuredperiodic grant of the first type. According to an embodiment, a failureof transmitting the one or more transport blocks may be determined inresponse to receiving no corresponding response from the base station.According to an embodiment, a counter may be incremented by one inresponse to determining the failure. According to an embodiment, the atleast one first message may comprise an identifier of the configuredperiodic grant of the first type. According to an embodiment, the secondmessage may comprise the identifier of the configured periodic grant ofthe first type. According to an embodiment, the third message maycomprise the identifier of the configured periodic grant of the firsttype.

FIG. 38 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 3810, a base station may transmit at leastone first message to a wireless device. The at least one first messagemay comprise at least one configuration parameter. The at least oneconfiguration parameter may indicate a timing offset and a symbol numberthat identify a resource of an uplink grant of a configured periodicgrant of a first type. The at least one configuration parameter mayindicate a first periodicity of the configured periodic grant of thefirst type. The first periodicity may indicate a time interval betweentwo subsequent resources of the configured periodic grant of the firsttype. At 3820, one or more transport blocks may be received via theresource of the configured periodic grant of the first type. At 3830, asecond message may be transmitted. The second message may indicate arequest for transmission information associated with the configuredperiodic grant of the first type. At 3840, a third message may bereceived in response to the second message. The third message maycomprise one or more parameters. The one or more parameters may indicateat least one of: a first value based on a number of transmissions viathe resource associated with the configured periodic grant of the firsttype; and a second value based on a number of times that the wirelessdevice received no corresponding acknowledgement from the base stationin response to the transmissions.

According to an embodiment, the at least one configuration parameter mayindicate a duration determining the first value and the second value.According to an embodiment, the configured periodic grant of the firsttype may be activated to start from a first symbol based on: the timingoffset; and the symbol number. The configured periodic grant of thefirst type may reoccur with the first periodicity. According to anembodiment, one or more symbols of the resource of the uplink grant ofthe configured periodic grant of the first type may be determined basedon the timing offset, the symbol number, and the first periodicity.According to an embodiment, the one or more parameters may indicate athird value based on a number of times that the wireless device receivesa positive or negative acknowledgement from the base station in responseto the transmissions via the resource of the configured periodic grantof the first type. According to an embodiment, the one or moreparameters may indicate a fourth value based on a number of collisionsdetected by the wireless device when the wireless device receives noacknowledgement from the base station in response to the transmissionsvia the configured periodic grant of the first type. According to anembodiment, the third message may comprise an indicator that indicateswhether the wireless device detects one or more collisions when thewireless device receives no acknowledgement from the base station inresponse to the transmissions via the configured periodic grant of thefirst type. According to an embodiment, the at least one configurationparameter may comprise a power offset value determining a transmit powerfor a transmission of the one or more transport blocks. According to anembodiment, the at least one first message may comprise an identifier ofthe configured periodic grant of the first type. According to anembodiment, the second message may comprise the identifier of theconfigured periodic grant of the first type. According to an embodiment,the third message may comprise the identifier of the configured periodicgrant of the first type.

In this specification, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” In this specification,the term “may” is to be interpreted as “may, for example.” In otherwords, the term “may” is indicative that the phrase following the term“may” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.If A and B are sets and every element of A is also an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1}, {cell2}, and {cell1, cell2}.

In this specification, parameters (Information elements: IEs) maycomprise one or more objects, and each of those objects may comprise oneor more other objects. For example, if parameter (IE) N comprisesparameter (IE) M, and parameter (IE) M comprises parameter (IE) K, andparameter (IE) K comprises parameter (information element) J, then, forexample, N comprises K, and N comprises J. In an example embodiment,when one or more messages comprise a plurality of parameters, it impliesthat a parameter in the plurality of parameters is in at least one ofthe one or more messages, but does not have to be in each of the one ormore messages.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an isolatableelement that performs a defined function and has a defined interface toother elements. The modules described in this disclosure may beimplemented in hardware, software in combination with hardware,firmware, wetware (i.e hardware with a biological element) or acombination thereof, all of which are behaviorally equivalent. Forexample, modules may be implemented as a software routine written in acomputer language configured to be executed by a hardware machine (suchas C, C++, Fortran, Java, Basic, Matlab or the like) or amodeling/simulation program such as Simulink, Stateflow, GNU Octave, orLabVIEWMathScript. Additionally, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers and microprocessors are programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDsare often programmed using hardware description languages (HDL) such asVHSIC hardware description language (VHDL) or Verilog that configureconnections between internal hardware modules with lesser functionalityon a programmable device. Finally, it needs to be emphasized that theabove mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the spirit and scope. After reading the abovedescription, it will be apparent to one skilled in the relevant art(s)how to implement alternative embodiments. Thus, the present embodimentsshould not be limited by any of the above described exemplaryembodiments. In particular, it should be noted that, for examplepurposes, the above explanation has focused on the example(s) using FDDcommunication systems. However, one skilled in the art will recognizethat embodiments of the disclosure may also be implemented in a systemcomprising one or more TDD cells (e.g. frame structure 2 and/or framestructure 3-licensed assisted access). The disclosed methods and systemsmay be implemented in wireless or wireline systems. The features ofvarious embodiments presented in this disclosure may be combined. One ormany features (method or system) of one embodiment may be implemented inother embodiments. Only a limited number of example combinations areshown to indicate to one skilled in the art the possibility of featuresthat may be combined in various embodiments to create enhancedtransmission and reception systems and methods.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposesonly. The disclosed architecture is sufficiently flexible andconfigurable, such that it may be utilized in ways other than thatshown. For example, the actions listed in any flowchart may bere-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112. Claims that do not expressly include the phrase “means for”or “step for” are not to be interpreted under 35 U.S.C. 112.

What is claimed is:
 1. A method by a user equipment (UE) in a wirelesscommunication system, the method comprising: receiving, from a basestation, a radio resource control (RRC) message comprising a parameterindicating whether a configured grant type 1 is used for transmission ofdata from a logical channel; activating the configured grant type 1 inresponse to the parameter indicating the configured grant type 1 is usedfor transmission of the data from the logical channel; and transmitting,to the base station, one or more transport blocks associated with thedata of the logical channel based on the configured grant type
 1. 2. Themethod of claim 1, wherein the RRC message further comprises at leastone of an identifier (ID) of a logical channel group to which thelogical channel belongs, a timing offset associated with a system framenumber, and information on a start symbol for identifying a resource tobe allocated by the configured grant type
 1. 3. The method of claim 1,further comprising: multiplexing the data of the logical channel ontothe one or more transport blocks.
 4. The method of claim 2, wherein theconfigured grant type 1 is used for resource allocation starting from afirst symbol allocated based on the timing offset and the information onthe start symbol.
 5. The method of claim 1, wherein the RRC messagefurther comprises a first periodicity of a configured periodic grant ofa first type, the first periodicity indicating a time interval betweentwo subsequent resources of the configured periodic grant of the firsttype, and wherein resource allocation reoccurs with the firstperiodicity.
 6. A method by base station in a wireless communicationsystem, the method comprising: transmitting, to a user equipment (UE), aradio resource control (RRC) message comprising a parameter indicatingwhether a configured grant type 1 is used for transmission of data froma logical channel; and receiving, from the UE, one or more transportblocks associated with the data of the logical channel based on theconfigured grant type 1, wherein the configured grant type 1 isactivated in response to the parameter indicating the configured granttype 1 is used for transmission of the data from the logical channel. 7.The method of claim 6, wherein the RRC message further comprises atleast one of an identifier (ID) of a logical channel group to which thelogical channel belongs, a timing offset associated with a system framenumber, and information on a start symbol for identifying a resource tobe allocated by the configured grant type
 1. 8. The method of claim 7,wherein the configured grant type 1 is used for resource allocationstarting from a first symbol allocated based on the timing offset andthe information on the start symbol.
 9. The method of claim 6, whereinthe RRC message further comprises a first periodicity of a configuredperiodic grant of a first type, the first periodicity indicating a timeinterval between two subsequent resources of the configured periodicgrant of the first type, and wherein resource allocation reoccurs withthe first periodicity.
 10. A user equipment (UE) in a wirelesscommunication system, the UE comprising: a transceiver; and a controllercoupled with the transceiver and configured to control to: receive, froma base station, a radio resource control (RRC) message comprising aparameter indicating whether a configured grant type 1 is used fortransmission of data from a logical channel, activate the configuredgrant type 1 in response to the parameter indicating the configuredgrant type 1 is used for transmission of the data from the logicalchannel, and transmit, to the base station, one or more transport blocksassociated with the data of the logical channel based on the configuredgrant type
 1. 11. The UE of claim 10, wherein the RRC message furthercomprises at least one of an identifier (ID) of a logical channel groupto which the logical channel belongs, a timing offset associated with asystem frame number, and information on a start symbol for identifying aresource to be allocated by the configured grant type
 1. 12. The UE ofclaim 10, wherein the controller is configured to: multiplex the data ofthe logical channel onto the one or more transport blocks.
 13. The UE ofclaim 11, wherein the configured grant type 1 is used for resourceallocation starting from a first symbol allocated based on the timingoffset and the information on the start symbol.
 14. The UE of claim 10,wherein the RRC message further comprises a first periodicity of aconfigured periodic grant of a first type, the first periodicityindicating a time interval between two subsequent resources of theconfigured periodic grant of the first type, and wherein resourceallocation reoccurs with the first periodicity.
 15. A base station in awireless communication system, the base station comprising: atransceiver; and a controller coupled with the transceiver andconfigured to control to: transmit, to a user equipment (UE), a radioresource control (RRC) message comprising a parameter indicating whethera configured grant type 1 is used for transmission of data from alogical channel, and receive, from the UE, one or more transport blocksassociated with the data of the logical channel based on the configuredgrant type 1, wherein the configured grant type 1 is activated inresponse to the parameter indicating the configured grant type 1 is usedfor transmission of the data from the logical channel.
 16. The basestation of claim 15, wherein the RRC message further comprises at leastone of an identifier (ID) of a logical channel group to which thelogical channel belongs, a timing offset associated with a system framenumber, and information on a start symbol for identifying a resource tobe allocated by the configured grant type
 1. 17. The base station ofclaim 16, wherein the configured grant type 1 is used for resourceallocation starting from a first symbol allocated based on the timingoffset and the information on the start symbol.
 18. The base station ofclaim 15, wherein the RRC message further comprises a first periodicityof a configured periodic grant of a first type, the first periodicityindicating a time interval between two subsequent resources of theconfigured periodic grant of the first type, and wherein resourceallocation reoccurs with the first periodicity.